You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a secondary service that's deployed from my app's repo via a separate configuration file.
I can deploy the secondary service with kamal deploy --config-file=config/other.deploy.yml and that command succeeds.
I tried to make this command an alias in my main app's config/deploy.yml, but I get a registry error because the secondary service uses a different registry but kamal tries to use the main app's registry to pull the image:
docker stderr: Unable to find image main.myregistry.com/secondary:latest' locally
When in config/other.deploy.yml, I have the registry.server set to other.myregistry.com.
My alias configuration in config/deploy.yml looks like:
If I'm using kamal in an unintended way please tell me 😅. But it would be nice if I could configure an alias to deploy my secondary service so I don't have to add --config-file=config/other.deploy.yml every time.
The text was updated successfully, but these errors were encountered:
djmb
linked a pull request
Oct 2, 2024
that will
close
this issue
I have a secondary service that's deployed from my app's repo via a separate configuration file.
I can deploy the secondary service with
kamal deploy --config-file=config/other.deploy.yml
and that command succeeds.I tried to make this command an alias in my main app's
config/deploy.yml
, but I get a registry error because the secondary service uses a different registry but kamal tries to use the main app's registry to pull the image:When in
config/other.deploy.yml
, I have theregistry.server
set toother.myregistry.com
.My alias configuration in
config/deploy.yml
looks like:If I'm using kamal in an unintended way please tell me 😅. But it would be nice if I could configure an alias to deploy my secondary service so I don't have to add
--config-file=config/other.deploy.yml
every time.The text was updated successfully, but these errors were encountered: