Unable to run NextCloud AIO in Docker Desktop

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • I am unsure. I downloaded the latest from here: https://hub.docker.com/r/nextcloud/all-in-one. However, don't see a version number and the container will not even run.
  • Operating system and version (e.g., Ubuntu 24.04):
    • Kubuntu 2404
  • Web server and version (e.g, Apache 2.4.25):
    • Unknown. I am attempting to run Nextcloud within Docker Desktop v4.44.3
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • N/A
  • PHP version (e.g, 8.3):
    • Unknown
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • After attempting the run the image
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Docker
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

I am attempting to run NextCloud AIO on Docker Desktop v4.44.3 (Engine: 28.3.2) running on Kubuntu 24.04. When I attempt to run the container, whether from the GUI or CLI, I get:

Docker socket is not available. Cannot continue.

Please make sure to mount the docker socket into /var/run/docker.sock inside the container!

I have looked at many posts and articles within the docker but have yet to find a solution for this issue.

Steps to replicate it (hint: details matter!):

  1. Open Docker Desktop
  2. Click on Containers
  3. Click Start on the NextCloud Container
2

Hi, did you follow GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.?

1 Like
3

Yes I did. I have attempted running it from the desktop and using the command referenced in that article.

I also tried adding the --security-opt label=disabled option to the command as suggested in Docker socket is not available. · nextcloud/all-in-one · Discussion #485 · GitHub to no avail.

4

If I am not mistaken, on Desktop Linux (Ubuntu/Kubuntu 24.04) the issue is that Docker Desktop does not use the standard socket /var/run/docker.sock, but its own one (for example in $HOME/.docker/desktop/docker.sock).
Nextcloud AIO, however, is designed to require access specifically to /var/run/docker.sock. That’s why it fails when running under Docker Desktop.

Docker Desktop makes sense on Windows/macOS, but on Linux it usually causes more problems than it solves. The simpler and more stable option is to install Docker Engine directly.

Install Docker Engine on Ubuntu/Kubuntu 24.04

curl -fsSL get.docker.com | sudo sh
sudo usermod -aG docker $USER

(Then reboot your device so the group membership is applied.)

Verify it works:

docker run --rm hello-world

Running Nextcloud AIO

After this setup you have the standard /var/run/docker.sock available, so AIO will run without issues.
You can start it either with the official docker run command from the README, or – as I personally prefer – with a docker-compose.yml file.

1 Like