I recently deployed ODK aggregate v2.0.5 to a server using docker-compose. As part of this I decided to automate the build of a docker image from the github repo via github actions (instead of running build scripts on my own computer or the hosting server first).
Hi @dkonan ,
I'm afraid I haven't looked at this in a while so I'm not really sure what the problem might be, but you might get some more clues if you check the logs for the container. You can do this via the docker logs <container ID> command.
You can get the ID of the container via docker ls command if running (or docker ls -a if not), and just need to type the first few letters of the ID (whatever will uniquely identify it)
E.g., docker ls
CONTAINER ID IMAGE COMMAND CREATED STATUS
fcae22fa4144 xyz/my-image:latest "/opt/bin/entrypoint-" 2 hours ago Up 2 minutes
155206af2f03 abc/my-image:latest "/entrypoint.sh mysql" 2 hours ago Up 2 minutes
docker logs fc
Will give the logs of the container with id fcae22fa4144
Thanks, that's really useful. I can see from the first line that postgres specifies that a superuser password must be provided. I've modified the github gist above to include an environment field for the db where this can be specified or to allow connections without a password.