Unable to create a workspace from a private image from dockerhub

[Keith-Hon]

Bug description

Reference: #8550 (comment)

Using a private image from dockerhub will cause the below error

Steps to reproduce

1. Build a docker image from one of the gitpod workspace images, e.g. gitpod/workspace-full:2022-06-20-19-54-55
2. Publish that image with scope to dockerhub, so that the image is private
3. Create a new git repository and edit .gitpod.yml with reference of the private image
4. Start a new workspace on such repository
5. Error occurs

Workspace affected

No response

Expected behavior

It should successfully start a new workspave with a private docker image from dockerhub

Example repository

No response

Anything else?

Related Discord discussion: https://discord.com/channels/816244985187008514/1006133715409313882

[kapke]

Hi! I'm playing with gitpod and I have run into exactly the same issue. I have a private repo and a private dockerhub image. Gitpod cannot build/load the image because of exactly the same error as in the original post.
Sadly, neither the repo or image can be made public.

[axonasif]

Is your repo private as well @kapke?

[kapke]

@axonasif Yes, it is. Will Dockerfile like

FROM my-private-image

work in such case?

[axonasif]

No @kapke, I mean to put your dockerfile contents into that file, souring it externally with FROM would not help for now.

[kapke]

I see. Sadly this is way beyond what's easy for the environment I need.
On the other hand, Nix with flakes does the job just fine in my case, I looked at Docker mostly to have the workspace load instantly instead of having to wait couple of minutes for Nix to fetch everything.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.