Using the local kind registry from kn quickstart, I am getting a little issue.
Running the first deploy is good:
func deploy --registry localhost:5001
Building function image
Still building
🙌 Function built: localhost:5001/s3-logger:latest
Pushing function image to the registry "localhost:5001" using the "" user credentials
⬆️ Deploying function to the cluster
🎯 Creating Triggers on the cluster
✅ Function deployed in namespace "default" and exposed at URL:
http://s3-logger.default.127.0.0.1.sslip.io
Now, running it for a second time (and yes, no code changes), I am getting an error:
➜ s3-logger func deploy --registry localhost:5001
function up-to-date. Force rebuild with --build
Pushing function image to the registry "localhost:5001" using the "" user credentials
Error: Error response from daemon: failed to find image localhost:5001/s3-logger@sha256:82e961f6b4868a296547f477cec305af1048c4e9785bdc23e71088612675c42c: localhost:5001/s3-logger@sha256:82e961f6b4868a296547f477cec305af1048c4e9785bdc23e71088612675c42c: No such image
there is a work-around, by forcing the rebuild to happen, using the --build argument:
➜ s3-logger func deploy --build --registry localhost:5001
Building function image
Still building
🙌 Function built: localhost:5001/s3-logger:latest
Pushing function image to the registry "localhost:5001" using the "" user credentials
⬆️ Deploying function to the cluster
🎯 Creating Triggers on the cluster
✅ Function updated in namespace "default" and exposed at URL:
Using the local kind registry from
kn quickstart
, I am getting a little issue.Running the first
deploy
is good:Now, running it for a second time (and yes, no code changes), I am getting an error:
there is a work-around, by forcing the rebuild to happen, using the
--build
argument:NOTE: I am running w/ podman - not the docker CLI