Issue when using n8n-caddy

Questions
#1

I’m seeing this error when I’m trying to run docker-compose:

Cannot stop container: <id>: permission denied

I understand that I should have ran docker-compose down but I’m also having an issue doing so. It complains both permission denied and network n8n-docker-caddy_default has active endpoints.

This is odd since I was able to run docker-compose down before and had no issues with running these commands. I’ve tried multiple things that online forums have recommended such as running docker network prune or removing orphans or removing the network directly. Nothing seems to be working for me.

Anyone know how I can successfully shut these containers down so I can build my new one with the new n8n versions?

Information on your n8n setup

  • n8n version: 0.215.1
  • Database you’re using (default: SQLite): Default (SQLite)
  • Running n8n with the execution process [own(default), main]: Default (own)
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker (caddy)
#2

Hey @soba-james,

That looks like docker is telling you that your user doesn’t have permission to stop the container, Have you tried doing it as root?

#3

Hi, I am logged in as root, I’ve also tried sudo commands and it just doesn’t seem to work

#4

@soba-james If you are on Linux, can you please check if you have AppArmor active?

Also, please do not delete the Information on your n8n setup section when creating new posts, that’s very important information, and is often helpful in figuring out the issues quicker.

#5

@netroy Updated n8n setup information. Here’s my AppArmor setup:

apparmor module is loaded.
27 profiles are loaded.
27 profiles are in enforce mode.
   /snap/snapd/17950/usr/lib/snapd/snap-confine
   /snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /snap/snapd/18357/usr/lib/snapd/snap-confine
   /snap/snapd/18357/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   docker-default
   snap-update-ns.docker
   snap-update-ns.lxd
   snap.docker.compose
   snap.docker.docker
   snap.docker.dockerd
   snap.docker.help
   snap.docker.hook.install
   snap.docker.hook.post-refresh
   snap.docker.machine
   snap.lxd.activate
   snap.lxd.benchmark
   snap.lxd.buginfo
   snap.lxd.check-kernel
   snap.lxd.daemon
   snap.lxd.hook.configure
   snap.lxd.hook.install
   snap.lxd.hook.remove
   snap.lxd.lxc
   snap.lxd.lxc-to-lxd
   snap.lxd.lxd
   snap.lxd.migrate
   snap.lxd.user-daemon
0 profiles are in complain mode.
0 profiles are in kill mode.
0 profiles are in unconfined mode.
13 processes have profiles defined.
13 processes are in enforce mode.
   /sbin/tini (1624) docker-default
   /usr/local/bin/node (1673) docker-default
   /usr/bin/caddy (2165) docker-default
   /snap/docker/2343/bin/dockerd (769) snap.docker.dockerd
   /snap/docker/2343/bin/containerd (1304) snap.docker.dockerd
   /snap/docker/2343/bin/docker-proxy (1581) snap.docker.dockerd
   /snap/docker/2343/bin/docker-proxy (1588) snap.docker.dockerd
   /snap/docker/2343/bin/containerd-shim-runc-v2 (1603) snap.docker.dockerd
   /snap/docker/2343/bin/docker-proxy (2103) snap.docker.dockerd
   /snap/docker/2343/bin/docker-proxy (2109) snap.docker.dockerd
   /snap/docker/2343/bin/docker-proxy (2124) snap.docker.dockerd
   /snap/docker/2343/bin/docker-proxy (2131) snap.docker.dockerd
   /snap/docker/2343/bin/containerd-shim-runc-v2 (2144) snap.docker.dockerd
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
0 processes are in mixed mode.
0 processes are in kill mode.
#6

Was able to get past this issue by stopping docker overall. If anyone ran into a similar issue, let me know and I can share the steps.

1 Like