-
-
Notifications
You must be signed in to change notification settings - Fork 436
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
Unable to login on AWS registry when using containerd
#171
Comments
You probably need to update |
@ViBiOh you can override the inbuilt nerdctl by following this #105 (comment). If that does fixes it, I would make a version bump for the nerdctl 0.16.1. |
That's what I was looking for, testing with an up-to-date So if you have time for bumping to the 0.16.1, it will be great =) |
Ah yes, my bad, I forgot for a moment that in the Alpine image |
@ViBiOh can you give this a try and see if it's fixed? https://github.com/abiosoft/colima/releases/tag/v0.3.3-pre-02 |
Perhaps there is also a similar problem #164, preventing building from public ECR. |
It works out of the box 👍 |
First of all, thank you for bringing alternative to Docker Desktop 😌 It works like a charm =)
But, I have a problem :p
When using colima with
containerd
runtime, I cannot login to the AWS registry using thenerdctl login
(that I have aliased todocker
command). Regular login to the "Official" Docker registry works fine.The issue seems discuss and resolved on nerdctl. So is it about a dependencies update or I miss something?
I've tried running
lima
directly with nerdctl and it works (I guess the ubuntu image for containerd is more stuffed than the alpine used by colima).The text was updated successfully, but these errors were encountered: