Tried hosting n8n on Google Cloud but pod gives Error: command /bin/sh not found

Describe the problem/error/question

Followed the documentation on Google Cloud | n8n Docs

I’ve managed to deploy it into my GKE cluster but both the N8N pod and the Database pod are not working.

When checking the logs, I get: Error: command /bin/sh not found.

My guess is that this is related to this args in the n8n-deployment.yaml file in the repo GitHub - n8n-io/n8n-kubernetes-hosting

spec:
containers:
- args:
- /bin/sh
- -c
- sleep 5; n8n start

I pulled the image locally and the tried running it in interactive mode with: docker run -it --rm a263c0f9d88a /bin/sh

But I get the same message on my terminal
› Error: command /bin/sh not found

I know that running worker or start --tunnel wiil work or just runnig it without any args will also work. But my context here is GKE and I tried removing those args, or changing them and still can’t get it to work.

Since I’m following the official documentation, does anyone have any other suggestion?

What is the error message (if any)?

Error: command /bin/sh not found

Information on your n8n setup

  • n8n version: both latest and next
  • Database (default: SQLite): Postgress
  • n8n EXECUTIONS_PROCESS setting (default: own, main): ?
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Cloud self hosted GKE
  • Operating system: Kubernetes

I know that running worker or start --tunnel wiil work or just runnig it without any args will also work. But my context here is GKE and I tried removing those args, or changing them and still can’t get it to work.

I am so sorry for the trouble @Gustavo. I am not quite sure about the status of this repo and whether additional changes migth be required to make it work with n8n v1. Perhaps @netroy can help with this one?

@Gustavo The gcp branch on the n8n-kubernetes-hosting repo was lacking some v1 related fixes. We’ve rebased the branch now.
Can you please try again and let us know if this is fixed for you :pray: ?

3 Likes

Thanks guys. I’ts working now.

I pulled the new version and was able to deploy it on my cluster. The devs are working on configuring it now.

I’ll let you know if something comes up.

3 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.