Ok, I see. I Googled the error and the most common reasons were to do with apparmor, with the solution being to disable apparmor, remove the config for the command you’re running and then restart, however Docker’s apparmor config is generated at runtime and loaded straight into memory when Docker starts, so there’s no time to disable it.
I don’t imagine apparmor’s purpose is to stop things being restarted, rather to stop unauthorised people doing it …
I have managed to totally disable apparmor, and shut down the container, but it’s left things in a mess which I’m currently trying to clean up. I did that by shutting down aa, then disabling it.
I’ll sort that and see what I can come up about apparmor & docker, I’ve never used apparmor before, and maybe this is more of a question for Docker support than Home Assistant.
I can tell you that I have an Ubuntu 1804 server running docker compose just fine and I’ve never touched apparmor. I didn’t need to touch it, so it’s running the same as the day I stood up the server.
Installed docker-ce because it’s recommended over what’s in the Ubuntu repos, and installed docker-compose the normal way I guess. It was either through pip or apt