Error when running docker compose up -d on DigitalOcean

[demobiel]

Hi

I am following the tutorial on Digital Ocean - n8n Documentation to setup a n8n instance on Digital Ocean.

When I run docker compose up -d I get the following error:

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/root/n8n-docker-caddy/caddy_config/Caddyfile" to rootfs at "/etc/caddy/Caddyfile": mount /root/n8n-docker-caddy/caddy_config/Caddyfile:/etc/caddy/Caddyfile (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

I tried the following topic to solve my problem, but I think this is not the same issue:

Error: mounting caddy_config/Caddyfile to rootfs at 'etc/caddy/Caddyfile'

FIXED: the command docker-compose up -d apparenty creates a sibling folder to the n8n-docker-caddy called n8n-digital-ocean. This directory also has a caddy_config folder with a Caddyfile directory in it, probably created when i ran the command without moving the Caddyfile from local_files to caddy_config (see below). SOLUTION make sure the Caddyfile is in the caddy_config directory in n8n-docker-caddy. delete the Caddyfile directory from n8n-digital-ocean/caddy_config run docker-compose up …

I am a newbie to Docker… but in the end I just followed the tutorials. At the moment I am logged in as root, so I don’t think privileges might be a problem.

Kind regards

Andries

[MutedJam]

Hi @demobiel, welcome to the community!

I am not a digital ocean user and don’t know about the specifics of their landscape.

Seeing the error message suggests

Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

Can you confirm whether /root/n8n-docker-caddy/caddy_config/Caddyfile exists in your digital ocean droplet and is indeed a file? You could for example run cat /root/n8n-docker-caddy/caddy_config/Caddyfile to see the file content.