AIO - The 'nextcloud-aio-mastercontainer' container was not found

Can you run

sudo find / -name docker.sock and post the output here?

$ sudo find / -name docker.sock
/run/docker.sock
/run/user/1000/docker.sock
/home/ubuntu/.local/share/docker/vfs/dir/6edad21a876d359d2a79d0668a886a0576161dcf118d0c503e99c38c6e4da3b8/run/docker.sock

Found it. So apparently what I wrote is indeed the case :slight_smile:

/run/docker.sock is the normal docker socket
/run/user/1000/docker.sock is the rootless docker socket

that’s really odd… I’m starting to think this has to do with lxd… I’ve never had this coming up before. I’ll look into it and try to understand whats going on.
Thanks for taking the time to help me out!

1 Like

So I digged a bit more into this and I suspect what happened was I initially forgot to turn on nested virtualization on the LXD container for nextcloud, before installing docker.
As I recreated a new LXD container with nested virt before hand, after installing docker inside it, I now get:

Client: Docker Engine - Community
 Version:    24.0.2
 **Context:    default**
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.10.5
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.18.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

I’m now going to install nextcloud aio container.

EDIT: all working! Thanks again!

2 Likes