I am attempting to bring my company over from a docker-compose and Jenkins setup to Garden. I am running into a build failure, and can't make sense of what is going on. I get the following output:

Command "docker exec -i  crictl images --output=json docker.io/library/pgbouncer:v-67ed3bcc63" failed with code 1:

Seems like maybe it is missing the correct image name? This is running under debian. There's nothing interesting about the module or dockerfile afaict. Any ideas what might be going on here?

Hey there, we just wrapped our quarterly kick-off and this didn't get the attention it deserved. Have you tested using another Dockerfile or Docker image?

Hi. Thanks for getting back to me. Unfortunately, even the example application from the quickstart fails to build. The full output is too long, and is also automodded when I try to post. Essentially the same as above.

Hey imw, great that you are trying out garden 🙂 If you try with

garden build <service> -l4

there should be a bit more logs, could you paste a couple of more lines related to the failure for context?

Yes, for example:

Failed building worker. Here is the output:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Command "docker exec -i  crictl images --output=json docker.io/library/worker:v-4474f17920" failed with code 1:

Error: No such container:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[silly] Error: Command "docker exec -i  crictl images --output=json docker.io/library/worker:v-4474f17920" failed with code 1:

Error: No such container:
    at makeError (/snapshot/project/tmp/pkg/cli/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/snapshot/project/tmp/pkg/cli/node_modules/execa/index.js:114:26)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at exec (/snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/util/util.ts:215:17)
    at /snapshot/project/tmp/pkg/cli/node_modules/@garden-io/core/src/plugins/kubernetes/local/kind.ts:51:23

Error Details:

shortMessage: >-
  Command failed with exit code 1: docker exec -i  crictl images --output=json
  docker.io/library/worker:v-4474f17920
command: >-
  docker exec -i  crictl images --output=json
  docker.io/library/worker:v-4474f17920
exitCode: 1
stdout: ''
stderr: 'Error: No such container: '
all: 'Error: No such container: '
failed: true
timedOut: false
isCanceled: false
killed: false

Looking at the command itself:

docker exec -i  crictl images --output=json docker.io/library/worker:v-4474f17920

, there seems to be an extra space between

-i

and

crictl

. Like its missing something...

garden build worker --env=local

, maybe it cannot find your local kubernetes cluster?

I agree it seems to be missing the container name. I am using

kind

for a local cluster. Running the suggested gets the same error.

Not sure I can repro this on a mac, but this looks like a bug to me.

I could try again with k3s. Will give that a shot and let you know how it goes.

Tried to repro with kind on a mac, but it works. I did follow, https://docs.garden.io/guides/local-kubernetes#kind, to create the kind cluster and then configured ingress manually as in the workaround here: https://github.com/garden-io/garden/issues/3436

Hmm. Thanks for trying - my kind cluster was also set up using those instructions.

Have you tried Docker desktop? It has ingress setup out of the box @blue-lunch-98125

Ah, I didn't realize there was a linux build for it. I'll give that a shot as well.

@blue-lunch-98125 did you have a chance to test with Docker Desktop?

Also rancher desktop now has a Kubernetes solution that includes a Traefik ingress, I might give that one a try as well later to provide different alternatives for local-ingress

@bright-policeman-43626 (assuming you already know this but just in case) make sure you switch to using the Moby runtime with RD as we don't support the containerd runtime currently

Yes! That’s true, already experimented some issues because of that, definitely we need to use Moby instead of containerd