Replies: 4 comments 6 replies
-
I believe for Digital Ocean specifically you must use your registered account email address as the registry username |
Beta Was this translation helpful? Give feedback.
-
@bntzio for DigitalOcean you should add account name to the server address. Below is the config that works in one of my deploys.
|
Beta Was this translation helpful? Give feedback.
-
@bntzio |
Beta Was this translation helpful? Give feedback.
-
Not sure who needs this, but this worked for me: # Name of the container image.
image: registryname/app_name
# Credentials for your image host.
registry:
server: registry.digitalocean.com
username:
- KAMAL_REGISTRY_USERNAME
password:
- KAMAL_REGISTRY_PASSWORD and my
|
Beta Was this translation helpful? Give feedback.
-
I'm trying to deploy a rails app with kamal by pushing the app image to the digital ocean registry instead of the default registry (which is docker hub) but I'm getting an authentication error:
Using:
Steps to reproduce:
kamal
and modify thedeploy.yml
config file to set up hosts, traefik, volumes, and registryKAMAL_REGISTRY_PASSWORD
in the.env
file, along withRAILS_MASTER_KEY
kamal setup
My
KAMAL_REGISTRY_PASSWORD
is a Digital Ocean personal access token with scopesregistry (4): create, read, update, delete
(I've also tried with a full access scope and the same error is thrown).Seems that Digital Ocean stores the image layers in Digital Ocean Spaces which in turn requires its own Spaces Key to access, that's my guess.
Beta Was this translation helpful? Give feedback.
All reactions