Replies: 7 comments 1 reply
-
|
@jotka how should this work? |
Beta Was this translation helpful? Give feedback.
-
|
any news? |
Beta Was this translation helpful? Give feedback.
-
|
hi @AndreaF17 any debug logs from hawser? I think it's this case #1145 |
Beta Was this translation helpful? Give feedback.
-
|
the expected behavior is credentials are propagated to remote hawser. there is no need to authenticate on every remote host manually. |
Beta Was this translation helpful? Give feedback.
-
|
Did you have any updates, or am i missing something? |
Beta Was this translation helpful? Give feedback.
-
|
From testing i confirm that is probably a bug of dockhand. |
Beta Was this translation helpful? Give feedback.
-
|
@AndreaF17 i need hawser DEBUG logs, switch the log level, please and try again |
Beta Was this translation helpful? Give feedback.




Uh oh!
There was an error while loading. Please reload this page.
-
I’m trying to pull images from a private Docker registry using Dockhand.
The registry credentials are configured globally in the Dockhand management UI, and image pulls work correctly on the host where Dockhand itself is running.
However, when deploying or pulling the same image on remote hosts/environments managed by Dockhand, I consistently get:
What I Expected
I expected the registry credentials configured globally in Dockhand to also be used by remote environments/hosts.
Current Behavior
authentication requiredQuestion
Is this the expected behavior?
Do registry credentials need to be configured individually on each remote host/environment, even if they are already defined globally in Dockhand?
Beta Was this translation helpful? Give feedback.
All reactions