Unable to deploy built docker image when using a virtual cluster via vcluster

Open
#6,023 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, kubernetes
Domain
devops, infrastructure

Research direction

Start by reproducing the reported docker push failure for docker.io/osf/admin while kubectl targets a vcluster, then trace how Tilt handles built-image storage and registry access in that setup. Done means a built image can be pushed and deployed to the virtual cluster, or the supported workaround is documented.

Written by the indexing model from the issue text.

Description

bug

I am experimenting with using vclusters and I almost have everything working except for one last piece. It seems tilt has no problem pushing most things to a virtual cluster (helm charts, namespaces etc...) however it seems to fail when trying to build and push my own docker image. I guess it somehow doesn't have access to where images get stored when kubectl is pointed at the virtual cluster?

Build Failed: docker push: pushing image "docker.io/osf/admin": denied: requested access to the resource is denied

Is there any possible workaround to this?

Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tilt-dev/tilt

All issues in tilt-dev/tilt

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.