You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tilt should detect that OrbStack is running locally and not try to push images to Docker Hub.
STEP 2/3 — Pushing my-image:tilt-b40c5c3a04bf57c3
Skipping push: building on cluster's container runtime
Current Behavior
Tilt tries to push images to Docker Hub (when OrbStack was just started).
STEP 2/3 — Pushing my-image:tilt-b40c5c3a04bf57c3
Pushing with Docker client
Authenticating to image repo: docker.io
Sending image data
Build Failed: docker push: pushing image "docker.io/my-image": denied: requested access to the resource is denied
Steps to Reproduce
Install OrbStack
Run the following script:
orb start k8s
kubectl config use-context orbstack
while ! kubectl get node &> /dev/null; do
echo "Waiting for Kubernetes to be ready"
sleep 1
done
tilt doctor
tilt up
Notice that Tilt tries to push docker images to Docker Hub (only when not cached and OrbStack was just started)
Context
tilt doctor Output (before running tilt up when it tries to push)
We're trying to automate the cluster setup, but when starting OrbStack followed by Tilt there is a race-condition in detecting the environment. Refreshing a resource does not resolve the issue. Restarting Tilt resolves the issue until the next full restart (including OrbStack). I would be happy if someone could tell me for which condition I need to wait in the script before running tilt up. From the tilt doctor output I can see that Tilt already knows that it is working with an OrbStack cluster, but the "push policy" relies on something else.
Uh oh!
There was an error while loading. Please reload this page.
Expected Behavior
Tilt should detect that OrbStack is running locally and not try to push images to Docker Hub.
Current Behavior
Tilt tries to push images to Docker Hub (when OrbStack was just started).
Steps to Reproduce
Context
tilt doctor
Output (before runningtilt up
when it tries to push)About Your Use Case
We're trying to automate the cluster setup, but when starting OrbStack followed by Tilt there is a race-condition in detecting the environment. Refreshing a resource does not resolve the issue. Restarting Tilt resolves the issue until the next full restart (including OrbStack). I would be happy if someone could tell me for which condition I need to wait in the script before running
tilt up
. From thetilt doctor
output I can see that Tilt already knows that it is working with an OrbStack cluster, but the "push policy" relies on something else.Maybe it is related to this: https://github.com/tilt-dev/tilt/blob/master/internal/docker/env.go#L71
The text was updated successfully, but these errors were encountered: