Registry login of workspace spec not working #2835
pim opened 1 day ago

I set up a simple remote workspace provisioner (test button yields hello from within a docker image so that works).

In my project settings I defined the workspace spec to point to my internal docker repository with an access token. Running a workspace yields errors about authentication:

Jul 01 14:30:07 sub.mydomain.com dockerd[1001]: time="2026-07-01T14:30:07.058880777+02:00" level=error msg="Not continuing with pull after error" error="errors:\ndenied: requested access to the resource is denied\nunauthorized: authentication required\n"
Jul 01 14:30:07 sub.mydomain.com dockerd[1001]: time="2026-07-01T14:30:07.059282473+02:00" level=info msg="Ignoring extra error returned from registry" error="unauthorized: authentication required"

HOWEVER, if I define the same docker registry settings in my provisioner, and not in workspace spec, THEN IT DOES WORK.

It is my understanding that workspace spec is supposed to overwrite provisioner settings of docker registry so it should have worked in the first place.

  • Robin Shen changed fields 1 day ago
    Name Previous Value Current Value
    Assignee
    robin
    wh
  • Work Horse commented 1 day ago

    Fixed in pr #78.

    Workspace spec registry logins were not applied correctly when pulling the container image. Unlike provisioner registry logins (which resolve variables via getFacade() at provision time), spec logins were passed straight into RegistryLoginFacade and could still contain unresolved variables such as @server_url@ or @workspace_token@.

    The fix adds RegistryLogin.getFacade() for workspace spec logins and merges spec logins over provisioner logins through WorkspaceContext.getRegistryLoginFacades().

1/1
Type
Bug
Priority
Normal
Assignee
Affected Versions
16.0.1
Labels
No labels
Issue Votes (0)
Watchers (2)
Reference
OD-2835
Please wait...
Connection lost or session expired, reload to recover
Page is in error, reload to recover