-
Notifications
You must be signed in to change notification settings - Fork 1.7k
skaffold dev does not rebuild image when using kind with registry #9345
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
We have noticed the same behaviour and can confirm the issue as well. |
Same. We have noticed the same issue in 2.10 |
Same issue here, I have to foce delete the whole docker hub repository to valid local image cache, but sometimes it doesn't works as well |
We have the same issue when using k0s with a registry. |
Same trouble here. We use skaffold Version:v2.10.1 embedded in the Goland Google Cloud Code plugin. We are force to git push (to generate a new tag) or to remove manually the related dirty image of the repitory (Google Artifact Registry). |
Seems to be fixed with the v2.11.0 which is now used with the Goland Google Cloud Code plugin |
Expected behavior
When running
skaffold dev
using a kind cluster with local registry enabled, editing the Dockerfile should cause the image to rebuild and the container should be re-deployed with the updated image.Actual behavior
The image is not rebuilt.
Information
v2.10.0
Steps to reproduce the behavior
examples/getting-started
kind
cluster with registry using this script: https://kind.sigs.k8s.io/docs/user/local-registry/skaffold dev -v info
RUN touch test.txt
test.txt
was not created in the container:kubectl exec -it getting-started -- ls
kind delete clusters "kind"; docker network disconnect --force kind kind-registry; docker container rm --force --volumes kind-registry
Logs from
skaffold dev -v info
:then after editing the Dockerfile:
On version 2.9.0, editing the Dockerfile results in these logs; I would expect
2.10.*
to have the same behavior:The text was updated successfully, but these errors were encountered: