-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Support] Easier updating of docker-compose instance? (SHA256) #552
Comments
Not sure exactly what you are having issues with my docker compose looks like this
Then I have a scheduled job on my server that checks every hour whether the server needs to be updated such as Are you building the image from scratch each time? |
I had the same issue and solved this by adding a watchtower service in my compose:
With this config it will check for updates, download if necessary and restart the container as needed once an hour. I use factoriotools/factorio:stable image, as latest is sometimes updated before the steam version |
I can recommend using the docker compose because it also contains auto update handling: |
First off, the project works wonderfully, thank you very much.
Currently, whenever I want to upgrade the server to one of the many, many updates of Factorio, it's not enough to just set version to latest. I have to also procure the latest SHA256 from the buildinfo.json file. This seems to defeat the point of having a version tagged "latest" in the first place.
Can you suggest/implement a way of being able to just provide a version number, or even just "latest", and have the SHA256 be grabbed from buildinfo.json automatically?
The text was updated successfully, but these errors were encountered: