Docker build for eHour not working about dockerfiles HOT 5 CLOSED

It was last pushed three days ago, from what I can see: (on https://hub.docker.com/r/tianon/ehour/)

When I run it, I run with a custom properties file (because otherwise, the image is hard-coded to use mysql as the DB host name, user as the user, and pass as the password) and a dedicated network for eHour and MySQL, something like this: (untested, but this is the gist of how I run it)

$ docker network create ehour
$ docker run -dit --name ehour-mysql --memory 512m --network ehour --network-alias mysql --stop-timeout 60 -v ehour-mysql:/var/lib/mysql -e MYSQL_RANDOM_ROOT_PASSWORD=1 -e MYSQL_USER=ehour -e MYSQL_PASSWORD=some-super-secure-random-string -e MYSQL_DATABASE=ehour mysql:5.7
$ cat ehour.properties
ehour.standalone.port=8000
ehour.database=mysql
ehour.database.url=mysql://ehour:some-super-secure-random-string@mysql:3306/ehour?zeroDateTimeBehavior=convertToNull&useOldAliasMetadataBehavior=true
ehour.database.checkouttimeout=2000
ehour.configurationType=DEPLOYMENT
ehour.translations=%ehour.home%/resources/i18n
ehour.database.cp=hikari
$ docker run -dit --name ehour --network ehour -v "$PWD/ehour.properties":/usr/local/ehour/home/conf/ehour.properties:ro tianon/ehour

I then use NGINX in front to deliver traffic from the host's port 80 to the eHour container's port 8000 for a particular hostname.

from dockerfiles.

Oh, right, and you'll also need to seed your database the first time you run it. I forgot about that bit -- the necessary SQL files are embedded into the image itself.

If you're getting a 503 when you access the server, you can use docker logs on the container to discover what the error is.

from dockerfiles.

Ok, I've pushed a short adapted version of this both in Git and to Docker Hub. 👍

from dockerfiles.

Thanks for the extra information.

The push to DockerHub seems indeed to occur on a daily basis, but the last BUILD (under the tab "Build Details" happenned 5 months ago. I am not sure what is the mechanism for the automated build to occur, but I suspect something it broken with that regards.

Thanks

from dockerfiles.

from dockerfiles.