Skip to content
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

Closed
ViBiOh opened this issue Feb 9, 2022 · 7 comments · Fixed by #174
Closed

Unable to login on AWS registry when using containerd #171

ViBiOh opened this issue Feb 9, 2022 · 7 comments · Fixed by #174
Milestone

Comments

@ViBiOh
Copy link

ViBiOh commented Feb 9, 2022

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 the nerdctl login (that I have aliased to docker 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).

> colima start --runtime=containerd
> colima nerdctl install --path "${HOME}/opt/bin/docker"
> aws --profile "shared-services-aws" ecr get-login-password --region "${AWS_REGION}" | docker login --username "AWS" --password-stdin "${AWS_SHARED_SERVICES_ACCOUNT_ID}.dkr.ecr.${AWS_REGION}.amazonaws.com"

time="2022-02-09T08:30:34Z" level=error msg="failed to call tryLoginWithRegHost" error="unexpected status code 404" i=0
time="2022-02-09T08:30:34Z" level=fatal msg="unexpected status code 404"
@jandubois
Copy link

You probably need to update nerdctl to 0.16.1. Even though lima 0.8.2 uses this version, it will not update an existing VM (nerdctl runs inside the VM and not on the host). So you will need to destroy and recreate your VM to get the update.

@abiosoft
Copy link
Owner

abiosoft commented Feb 9, 2022

You probably need to update nerdctl to 0.16.1. Even though lima 0.8.2 uses this version, it will not update an existing VM (nerdctl runs inside the VM and not on the host). So you will need to destroy and recreate your VM to get the 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.

@ViBiOh
Copy link
Author

ViBiOh commented Feb 9, 2022

You probably need to update nerdctl to 0.16.1. Even though lima 0.8.2 uses this version, it will not update an existing VM (nerdctl runs inside the VM and not on the host). So you will need to destroy and recreate your VM to get the 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 nerdctl and it works when in the last version =)

So if you have time for bumping to the 0.16.1, it will be great =)

@jandubois
Copy link

Ah yes, my bad, I forgot for a moment that in the Alpine image nerdctl is part of the ISO and not installed by Lima. Sorry about that!

@abiosoft
Copy link
Owner

abiosoft commented Feb 9, 2022

@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

@kigawas
Copy link

kigawas commented Feb 10, 2022

Perhaps there is also a similar problem #164, preventing building from public ECR.

@ViBiOh
Copy link
Author

ViBiOh commented Feb 10, 2022

@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

It works out of the box 👍

@abiosoft abiosoft added this to the v0.3.3 milestone Feb 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants