Replies: 10 comments 16 replies
-
|
I am also getting this. My config section for this is # Credentials for your image host.
registry:
username: myusername
# Always use an access token rather than real password when possible.
password:
- KAMAL_REGISTRY_PASSWORD
where What am I missing? Here's the output of |
Beta Was this translation helpful? Give feedback.
-
|
Now I also have this problem on my CI (gitlab selfhosted + external runner, amd64).
I guess it's the same issue. Any idea how to get rid of the credentials cache? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @r3cha 🙌 |
Beta Was this translation helpful? Give feedback.
-
|
@r3cha Thank you, bro! |
Beta Was this translation helpful? Give feedback.
-
|
I created a github issue for this: #1383 |
Beta Was this translation helpful? Give feedback.
-
|
This just happened to me after using another dockerhub account for work and then trying to deploy my own website with my credentials I was so confused but thank you so much! Hopefully this gets resolved soon |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone solved this? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @yaKashif can you check the name of the image container (prior the forward slash / ) and registry username if it's the same? If the image container name is not same with the registry name this might be the possible cause of the issue. |
Beta Was this translation helpful? Give feedback.
-
|
It is same. |
Beta Was this translation helpful? Give feedback.
-
|
adding I though it would default to that. |
Beta Was this translation helpful? Give feedback.
-
|
On my end I didn’t need to add the server as I also have the same
understanding that it would be the default.
…On Sat, Oct 19, 2024 at 14:41 Kashif ***@***.***> wrote:
adding server: registry.hub.docker.com in deploy.yml worked
I though it would default to that.
—
Reply to this email directly, view it on GitHub
<#896 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE7TRSJV5CWASUONDAZGKDZ4HWHXAVCNFSM6AAAAABLSGM22GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJYHEZTSOI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, I’m encountering an issue with kamal and my GitHub Actions workflow during deployment. On my local environment, both kamal deploy and kamal redeploy work without any issues. However, when I use kamal redeploy in the GitHub Actions workflow, the deployment fails. Strangely, if I switch it to kamal deploy in the workflow, it works perfectly. I'm using a Read, Write, Delete docker acess token. error is : Has anyone else faced this problem or have any insights on why kamal redeploy might be failing in the GitHub Actions environment but works fine locally? |
Beta Was this translation helpful? Give feedback.
-
|
I faced that issues with GitHub Action. After few hours, it started working again. I thought it must have hit rate limit of Docker Hub. In that case I should have received 429 instead of 401 though. Not sure what went wrong. Meanwhile, it was working fine when I triggered the flow from my laptop. |
Beta Was this translation helpful? Give feedback.
-
Strange because I have been trying all morning and it is still not working. |
Beta Was this translation helpful? Give feedback.
-
|
I think the issue is that "redeploy" doesn't login into the registry. It's mentioned in the docs. |
Beta Was this translation helpful? Give feedback.
-
|
Ah I must of missed that part. Thanks Tanna |
Beta Was this translation helpful? Give feedback.
-
|
I had this issue and solved it by doing |
Beta Was this translation helpful? Give feedback.
-
|
In my case, it simply started working again with no explanation. I am unsure at this point what the cause might have been but I can close it and someone else can re-open if they have a similar issue. |
Beta Was this translation helpful? Give feedback.
-
|
Ran into the same after changing registry configs. Running |
Beta Was this translation helpful? Give feedback.
-
|
It's an issue that must be addressed. I have multiple projects in my machine and its trying to log into other project's registry. For example: the first one works fine. The second project tries do log into the first and the second registry with the same KAMAL_REGISTRY_PASSWORD, obviously it will not work and it shows that something is very wrong with the Kamal code, including serious security issues. Clearing up the build every time works, but since we lose the cache, the deploy process takes much longer than needed. I think only @dhh can handle this. |
Beta Was this translation helpful? Give feedback.
-
|
Ran into the same issue. In my case, I had an uncommitted change in my secrets like that then got ignored. |
Beta Was this translation helpful? Give feedback.
-
|
Heyo, I have experienced this issue on a new project. I don't have a complete fix, but I think a big hint might be I was able to get past the issue by replacing Now, obviously that's a goofy work around but I think it might suggest some potential issues between locally configured Terminal/shells properly passing ENV variables when running |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone, I have been managing to deploy an app with Kamal with these Docker credentials for a few days with no issues but now I am getting the following error and I'm unsure as to why that might be happening.
The image is available in the registry and just to see if the token was bad I created a new one, added it to
.envand rankamal env pushbefore trying again but I still got the same error just like below, has anyone experienced this one?------ > exporting to image: ------ ERROR: failed to solve: failed to push dockerusername/service-name:4z484256423y7c90x2409efb385aa447df33b2fa: push access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failedNote
I run Kamal using the following alias (not the gem install):
alias kamal='docker run -it --rm -v "${PWD}:/workdir" -v "${HOME}/.ssh:/root/.ssh" -v "/run/host-services/ssh-auth.sock:/run/host-services/ssh-auth.sock" -e SSH_AUTH_SOCK="/run/host-services/ssh-auth.sock" -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/basecamp/kamal:latest'Beta Was this translation helpful? Give feedback.
All reactions