-
Notifications
You must be signed in to change notification settings - Fork 488
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
Remote builder failing when using "Using remote builder for native multi-arch" #783
Comments
Kamal is designed to EITHER use local or remote building. It's not designed for using both to produce a single multi-arch image. I don't even think that's possible. |
The first builder example in the docs uses both: That's what I was expecting to be able to do after reading https://kamal-deploy.org/docs/configuration/builders/ |
Lol. There goes my memory. cc @djmb |
@hundredwatt - that error is not coming from the remote builder, but from the host you are deploying to. It's pulling the image and complaining that it's not built for Your config should be right for building a mutli-platform image though! Could you try removing the builder |
I am getting the same errors as above This is my builder section
I have ran Here is my
Here is the last trace of my error
|
@kaka-ruto - could you post the |
@djmb I updated to Kamal 1.8.2 and ran Today, I noticed it never runs anything on the remote builder... maybe that's the issue 🧐 Notice in the logs below it only runs
Logs:
|
@djmb this is the output of
|
Ok, I think this one should be fixed now by #922. That's been released in v1.8.3. |
updated to 1.8.3 and it's working for me! 🎉 |
Excited for the fix but I'm, not sure what I'm doing wrong as I'm still getting the same error. For surety, this is my config
I have updated to v 1.8.3 and ran And this is the latest output
|
It's work for me. Mac M1
|
Summary
--platform arm64
images to my registry--platform amd64
Details
config/deploy.yml:
Error from remote builder:
Logs:
The host at is authenticated to registry.digitalocean.com:
Status
Posting here to see if anyone knows how to fix, otherwise I'll try to investigate further when I get time
The text was updated successfully, but these errors were encountered: