-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Unable to create a workspace from a private image from dockerhub #11982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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. |
Is your repo private as well @kapke? |
@axonasif Yes, it is. Will Dockerfile like
work in such case? |
No @kapke, I mean to put your dockerfile contents into that file, souring it externally with |
I see. Sadly this is way beyond what's easy for the environment I need. |
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. |
@Keith-Hon @kapke if you'd like to try this again, please try these docs, and if you continue to have trouble let us know? Happy to reopen the issue. |
Bug description
Reference: #8550 (comment)
Using a private image from dockerhub will cause the below error
Steps to reproduce
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
The text was updated successfully, but these errors were encountered: