docker-compose up returns error

[mdmelo]

Followed directions in readme, all went well until the docker-compose step:

mike@t430sDebian:/files/django3/SixieNote$ docker-compose --verbose up
compose.config.config.find: Using configuration files: ./docker-compose.yml,./docker-compose.override.yml
ERROR: compose.cli.main.main: The Compose file is invalid because:
Service front-end has neither an image nor a build context specified. At least one must be provided.

docker images appear OK:

mike@t430sDebian:/files/django3/SixieNote$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
sixienote_local_django dev 29133ca2c5ec About an hour ago 525MB
python 3.8-slim e8ad3533cb52 5 days ago 194MB

mike@t430sDebian:/files/django3/SixieNote$ docker --version
Docker version 19.03.8, build afacb8b7f0

the host is Debian 10:
mike@t430sDebian:/files/django3/SixieNote$ cat /etc/debian_version
10.3

mike@t430sDebian:/files/django3/SixieNote$ uname -a
Linux t430sDebian 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux

'make build-dev' succeeded:
...
Successfully built 29133ca2c5ec
Successfully tagged sixienote_local_django:dev

BTW, is it going to be possible to edit the Django code using PyCharm on the host with the application source code in the container? Thanks.

[mdmelo]

in case anyone else experiences this (im running docker 19.03.8) - you need to specify the docker-compose file explicitly via '-f'. Failure to do that yields the error mentioned above. Specifying the compose file explicitly allows all the containers to start. Have to figure out how to add that arg to pycharm. Guess the people who created this repo dont monitor issues.

[calvinhp]

Sorry, just saw this, I will get it fixed up and commited later this week when I have a momen.