-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix Docker image builds CI messing up :latest
, :stable
, and :dev
tags
#1414
Comments
same error after recent update :( |
my archive default has the issue also ConsequentlyI made a clean one with the errro too |
Looks like it caused by this recent commit ( |
thanks |
Came here to report this as well. I would suggest running the migrations in CI to avoid pushing broken images to |
I'd like to expand this question to all the alias tags. Because the deeper I dig, the more confusing it gets: Like rcarmo said, the vast majority of projects I use consider But now I've learned that there is also
And then there's also And finally, Moreover, I'd generally expect installation instructions to suggest the stable, production-ready version. But the Wiki uses Ideally, the tags would be migrated to something that aligns with common practices (either ' |
THIS |
There is CI to handle all the tags as you'd expect but I broke it a couple ways with a recent big push, sorry all! There are three issues that caused this:
I'm working on fixing it right now. The final state should be:
|
:latest
, :stable
, and :dev
tags
Ok I just fixed all the tags manually, and I'm pushing the CI fixes next.
$ docker pull archivebox/archivebox:latest
$ docker run archivebox/archivebox:latest version
0.7.2
ArchiveBox v0.7.2 COMMIT_HASH=315c9f3 BUILD_TIME=2024-04-24 22:43:51 1713998631
... $ docker pull archivebox/archivebox:stable
$ docker run archivebox/archivebox:stable version
0.7.2
ArchiveBox v0.7.2 COMMIT_HASH=315c9f3 BUILD_TIME=2024-04-24 22:43:51 1713998631
... $ docker pull archivebox/archivebox:main
$ docker run archivebox/archivebox:main version
0.7.2
ArchiveBox v0.7.2 COMMIT_HASH=315c9f3 BUILD_TIME=2024-04-24 22:43:51 1713998631
... $ docker pull archivebox/archivebox:0.7
$ docker run archivebox/archivebox:0.7 version
0.7.2
ArchiveBox v0.7.2 COMMIT_HASH=315c9f3 BUILD_TIME=2024-04-24 22:43:51 1713998631
... $ docker pull archivebox/archivebox:0.7.2
$ docker run archivebox/archivebox:0.7.2 version
0.7.2
ArchiveBox v0.7.2 COMMIT_HASH=315c9f3 BUILD_TIME=2024-04-24 22:43:51 1713998631
... These ^ are all built from the 315c9f3 commit (the
$ docker pull archivebox/archivebox:dev
$ docker run archivebox/archivebox:dev version
0.7.3
ArchiveBox v0.7.3+editable COMMIT_HASH=b4c3aa5 BUILD_TIME=2024-03-26 22:15:46 1711491346
... The docs and scripts now exclusively recommend
I've entirely removed references to
|
Out of curiosity, what setup are ya'll running that pulls new docker tags so quickly? Are you using watchtower or some other auto-updater? And is the interval set to instant or daily? Knowing how updates roll out and which users get them first helps me plan releases and tag updates in the future. (ArchiveBox collects no analytics, so even seemingly small info like this is very useful to me) |
Watchtower, yes. Daily updates for some containers, weekly for others.
|
Watchtower running twice a day |
Daily watchtower runs for me also. |
Starting log:
Describe the bug
docker not starting
Steps to reproduce
docker compose
ArchiveBox version
docker latest image (24/04/2024)
Thanks for help
The text was updated successfully, but these errors were encountered: