Open khift363 opened 2 days ago
how to manually specify the tag ?
how to manually specify the tag ?
You would use factoriotools/factorio:2.0.9 for 2.0.9 instead of stable.
You can see all the tags here: https://hub.docker.com/r/factoriotools/factorio/tags
I had the same problem just, i needed to remove hole images hole server and then install it again with the docker image and then the :latest worked and downloaded 2.0.9
I will look into it, I have the feeling something is wrong with the last recent update script changes.
Latest stable is now .9 not sure if the root cause is fixed.
nope i just triggered a build by pushing to master. It looks like the reason is since my lastest changes to the workflow, it does not trigger a build anymore. Not sure why.
So um the thing that happened on Factorio site was: they released a 2.0.9 version tagged as Experimental, and then (few hours later) swapped the tag to Stable. That's the cause imo.
There's also an issue where we're waiting for the docker hub to update with the new version, rather than getting it directly from Wube. I was looking at the code and it looks like the version that gets downloaded is whatever version tag the docker has, and when the hub hasn't updated it lags. For :latest and :stable I propose it should get the download from these links: https://factorio.com/get-download/stable/headless/linux64 https://factorio.com/get-download/experimental/headless/linux64 Edit: https://factorio.com/get-download/latest/headless/linux64 appears to point to the same as 'experimental' but is also an option
well now it is on an experimental branch 2.0.10
well now it is on an experimental branch 2.0.10
Its on 2.0.9 for me and also has the same on docker hub
Issue persists with 2.0.10
Currently the most recent stable version is 2.0.9. The front page of the project shows this as well, and there appears to be an automated update an hour ago that updated the tags to correspond with the release of 2.0.9. However, if you pull the docker image with the 'stable' tag, you get an image for 2.0.8, not 2.0.9.
This happened when 2.0.8 was the most recent stable version as well -- the 'stable' tag would pull 2.0.7, not 2.0.8. In both situations I've had to manually specify the tag to get the container to pull the correct version.