Closed abratashov closed 1 month ago
Solved this issue by changes from:
builder:
multiarch: false
=>
builder:
cache:
type: registry
remote:
arch: amd64
As result, Kamal runs it with a correct docker command:
docker buildx build --push --platform linux/amd64 --builder kamal-my-app-demo-native-remote -t registry.gitlab.com/user/my-app/my-app-demo:0a2e408b9e77d6e5e4a9c73be0ccd232edf4b6c5_uncommitted_026c0b9acf253cef -t registry.gitlab.com/user/my-app/my-app-demo:latest --cache-to type=registry,ref=registry.gitlab.com/user/my-app/my-app-demo-build-cache --cache-from type=registry,ref=registry.gitlab.com/user/my-app/my-app-demo-build-cache --label service="my-app-demo" --file Dockerfile .
So, I left this ticket open, because as I see multiarch: false
doesn't work correctly.
CPU architecture: uname -m
My machine: x86_64
Host: x86_64
I think something else is at play. I just built a new app using multiarch: false. Seems like maybe it's related to the registry. Feel free to open another ticket if you pin it down further, but I can't replicate it as-is.
Yes, sure!
P.S. David, thank you for empowering your great dreams! We've just successfully migrated from the hundred Ansible scripts into the few files of Kamal, it works, and it's fantastic!
I've added this setting to
deploy.yml
:When try to set up server, it fails with error
An image does not exist locally with the tag: registry.gitlab.com/user/my-app/my-app-demo
Full log:
Kamal: 1.4.0 Docker: 24.0.5 Ubuntu: 22.04