-
Notifications
You must be signed in to change notification settings - Fork 103
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
[BUG] Failing to pull images tagged with 0.3 #351
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
Try 0.3 tag, I should be more consistent with the naming there. I apologise.
…On Thu, Nov 21, 2019, at 12:58 PM, brianemwd wrote:
My understanding is that Mailman 3.3 was now available via docker. However I am getting the following error when testing this out:
docker pull maxking/mailman-core:0.3.0
Error response from daemon: manifest for maxking/mailman-core:0.3.0 not found: manifest unknown: manifest unknown
Please advise. Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#351?email_source=notifications&email_token=AAFC5VMYEDFAZVUKENUN76TQU3Y5XA5CNFSM4JQICGDKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3G46NA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFC5VPCXIOBKEJUCY2NGMDQU3Y5XANCNFSM4JQICGDA>.
--
thanks,
Abhilash Raj (maxking)
|
I did try the 0.3 tag and I received the same error message. |
Actually the error message is different: docker pull maxking/mailman-core:0.3 |
What version of docker are you using? |
Docker version 19.03.4 |
Can you retry once? Perhaps from a different machine?
|
This seems to be the same issues as listed at: |
Try out if this works for you: I made sure that this gets built on the docker hub, so it doesn't encounter the bug which seems to be related to using podman. Note the 0.3.0 is the tag. Should work for mailman-web too. |
That worked but Postorius is still at version 1.2.4 and Hyperkitty at 1.2.2. I don't that is correct. |
Did you recreate the container? I tested it out and the image seems to have the latest versions.
|
I did not know about the recreate container part however I did that and still running Postorius 2.4 and HK 2.2. Here were my steps: $ docker-compose stop I got the exact output you showed above but I am still running the older versions. |
I also tried running: docker-compose up -d --force-recreate Still same versions. |
docker ps -a |
I figured out the problem. I forgot to update the docker-compose.yaml file to use the new containers. I still blame maxking. :^) |
Glad that you got it figured it out, I did realize that could have been the problem but only after you figured it out yourself :) |
My understanding is that Mailman 3.3 was now available via docker. However I am getting the following error when testing this out:
docker pull maxking/mailman-core:0.3.0
Error response from daemon: manifest for maxking/mailman-core:0.3.0 not found: manifest unknown: manifest unknown
Please advise. Thanks!
The text was updated successfully, but these errors were encountered: