[GH-ISSUE #794] Installer failed installing docker - rerunning docker piece alone #1637

New Issue

GiteaMirror · 2026-04-16T08:21:53-05:00

GiteaMirror commented

2026-04-16 08:21:53 -05:00

Originally created by @djl0 on GitHub (May 28, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/794

Originally assigned to: @oschwartz10612 on GitHub.

Hi - I was going through the installer (ubuntu 22), and the installer failed to start docker (install worked) because there was no docker group. so i added the group, got docker working, but then when i re-started the installer, it finished, but seemed to not have docker containers it should have set up. I see the section in docs for doing manual install via docker, but I just want to know what commands are for the docker-compose section of installer, like is there anything at all different from just downloading the compose file here, putting my domain in wherever "example.com" appears and running docker compose up -d?

Thanks for the help

Originally created by @djl0 on GitHub (May 28, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/794 Originally assigned to: @oschwartz10612 on GitHub. Hi - I was going through the installer (ubuntu 22), and the installer failed to start docker (install worked) because there was no docker group. so i added the group, got docker working, but then when i re-started the installer, it finished, but seemed to not have docker containers it should have set up. I see the section in docs for doing manual install via docker, but I just want to know what commands are for the docker-compose section of installer, like is there anything at all different from just downloading the compose file [here](https://docs.fossorial.io/Getting%20Started/Manual%20Install%20Guides/docker-compose), putting my domain in wherever "example.com" appears and running docker compose up -d? Thanks for the help

GiteaMirror added the potential bug needs investigating labels 2026-04-16 08:21:54 -05:00

GiteaMirror closed this issue

2026-04-16 08:21:54 -05:00

GiteaMirror commented

2026-04-16 08:21:55 -05:00

@djl0 commented on GitHub (May 28, 2025):

I think I sorted it out. For future ref, there's a generated docker-compose.yml file in the working dir, and i ran the docker compose pull and up commands which are found in: b467d6afa1/install/main.go (L93)

@djl0 commented on GitHub (May 28, 2025): I think I sorted it out. For future ref, there's a generated docker-compose.yml file in the working dir, and i ran the docker compose pull and up commands which are found in: https://github.com/fosrl/pangolin/blob/b467d6afa198a4d77d6399d3418382b5081d7eae/install/main.go#L93

GiteaMirror commented

2026-04-16 08:21:56 -05:00

@cameron1982-ha commented on GitHub (May 28, 2025):

I got the same issui, says docker daemon cannot be connected:

=== Starting installation ===
Would you like to install and start the containers? (yes/no) (default: yes): yes
Pulling the container images...
unable to get image 'fosrl/gerbil:1.0.0': Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Error: failed to pull the containers: exit status 1

Tried first on Ubuntu 24.04, then on Debian 12.

Don't know, how to go on?

@cameron1982-ha commented on GitHub (May 28, 2025): I got the same issui, says docker daemon cannot be connected: > === Starting installation === Would you like to install and start the containers? (yes/no) (default: yes): yes Pulling the container images... unable to get image 'fosrl/gerbil:1.0.0': Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Error: failed to pull the containers: exit status 1 Tried first on Ubuntu 24.04, then on Debian 12. Don't know, how to go on?

GiteaMirror commented

2026-04-16 08:21:56 -05:00

@djl0 commented on GitHub (May 28, 2025):

@cameron1982-ha:

(all of these commands are being run by root on my vps)
Make sure docker is installed and running. run docker hello world:
docker run hello-world

if not running, try to start its service:
systemctl start docker

I had an issue about its group, so i had to add docker group:

systemctl daemon-reexec
systemctl restart docker

Now docker's hello world should work:
docker run hello-world

pull and start docker containers (your current dir should have the docker-compose.yml generated by installer)
docker compose -f docker-compose.yml up -d --force-recreate

@djl0 commented on GitHub (May 28, 2025): @cameron1982-ha: (all of these commands are being run by root on my vps) Make sure docker is installed and running. run docker hello world: `docker run hello-world` if not running, try to start its service: `systemctl start docker` I had an issue about its group, so i had to add docker group: ```groupadd docker systemctl daemon-reexec systemctl restart docker ``` Now docker's hello world should work: `docker run hello-world` pull and start docker containers (your current dir should have the docker-compose.yml generated by installer) `docker compose -f docker-compose.yml up -d --force-recreate`

GiteaMirror commented

2026-04-16 08:21:57 -05:00

@oschwartz10612 commented on GitHub (May 29, 2025):

I will have to look into this. I dont usually have a permission problem because the installer is being run as root and the docker socket is accessible by root. I wonder if it is a race condition and it simply is not running yet. Thats my best guess.

We probably need to wait for the docker socket to be available before moving on.

@oschwartz10612 commented on GitHub (May 29, 2025): I will have to look into this. I dont usually have a permission problem because the installer is being run as root and the docker socket is accessible by root. I wonder if it is a race condition and it simply is not running yet. Thats my best guess. We probably need to wait for the docker socket to be available before moving on.

GiteaMirror commented

2026-04-16 08:21:57 -05:00

@djl0 commented on GitHub (May 29, 2025):

I resolved my issue by adding the docker group.

groupadd docker

@cameron1982-ha my bad, I actually forgot to add that line. Run that, then the

systemctl daemon-reexec
systemctl restart docker

... and then continue with docker compose

@djl0 commented on GitHub (May 29, 2025): I resolved my issue by adding the docker group. `groupadd docker` @cameron1982-ha my bad, I actually forgot to add that line. Run that, then the ``` systemctl daemon-reexec systemctl restart docker ``` ... and then continue with docker compose

GiteaMirror commented

2026-04-16 08:21:57 -05:00

@kmanwar89 commented on GitHub (May 29, 2025):

I resolved my issue by adding the docker group.

groupadd docker

@cameron1982-ha my bad, I actually forgot to add that line. Run that, then the
systemctl daemon-reexec
systemctl restart docker
... and then continue with docker compose

Adding the group is part of Docker's recommended post-install steps for Linux, and they cover user permissons/rootless here, if that helps.

The groupadd command is one I have scripted when installing Docker on a new machine just to avoid this issue

@kmanwar89 commented on GitHub (May 29, 2025): > I resolved my issue by adding the docker group. > > `groupadd docker` > > [@cameron1982-ha](https://github.com/cameron1982-ha) my bad, I actually forgot to add that line. Run that, then the > > ``` > systemctl daemon-reexec > systemctl restart docker > ``` > > ... and then continue with docker compose Adding the group is part of Docker's [recommended post-install steps for Linux](https://docs.docker.com/engine/install/linux-postinstall/), and they cover user permissons/rootless [here](https://docs.docker.com/engine/security/rootless/), if that helps. The `groupadd` command is one I have scripted when installing Docker on a new machine just to avoid this issue

GiteaMirror commented

2026-04-16 08:21:58 -05:00

@kalikid021 commented on GitHub (May 30, 2025):

I just want to comment that this may be an issue with the docker package. I was installing docker as part of an agent for an agent, totally unrelated to pangolin, a couple days ago when installing docker on Open Media Vault (debian 12). I followed the docker install instructions from their website

https://docs.docker.com/engine/install/debian/

I ran into the same issue with docker not starting, and after troubleshooting the issue I discovered that the none of the packages created the docker group, after manually creating it, everything ran fine.

Just for clarity, I have installed docker dozens of times on linux distros ,over the past year, and not one single time have I had to manually create the docker group. Perhaps this is a new change for docker since they are trying to move toward a rootless setup?

@kalikid021 commented on GitHub (May 30, 2025): I just want to comment that this may be an issue with the docker package. I was installing docker as part of an agent for an agent, totally unrelated to pangolin, a couple days ago when installing docker on Open Media Vault (debian 12). I followed the docker install instructions from their website https://docs.docker.com/engine/install/debian/ I ran into the same issue with docker not starting, and after troubleshooting the issue I discovered that the none of the packages created the docker group, after manually creating it, everything ran fine. Just for clarity, I have installed docker dozens of times on linux distros ,over the past year, and not one single time have I had to manually create the docker group. Perhaps this is a new change for docker since they are trying to move toward a rootless setup?

GiteaMirror commented

2026-04-16 08:21:58 -05:00

@cameron1982-ha commented on GitHub (May 30, 2025):

Today I did the same steps like a few days before... now the installer progress went well and I got pangolin up and running on a remote host. Nothing changed from my side, maybe the installer script was updated. However, docker runs and pangolin although.

Thanks a lot.

@cameron1982-ha commented on GitHub (May 30, 2025): Today I did the same steps like a few days before... now the installer progress went well and I got pangolin up and running on a remote host. Nothing changed from my side, maybe the installer script was updated. However, docker runs and pangolin although. Thanks a lot.

GiteaMirror commented

2026-04-16 08:21:58 -05:00

@oschwartz10612 commented on GitHub (May 31, 2025):

I think this may be fixed by cd280d1396 and d18200739a. Testing...

@oschwartz10612 commented on GitHub (May 31, 2025): I think this may be fixed by cd280d13967e079f612abe81f396b8a098db0aa1 and d18200739a73fc695f6e77eae118c2f432915cf7. Testing...

GiteaMirror commented

2026-04-16 08:21:59 -05:00

@kalikid021 commented on GitHub (May 31, 2025):

At least this will point the user in the direction of docker if it fails to start/install properly with some feedback. 👍

@kalikid021 commented on GitHub (May 31, 2025): At least this will point the user in the direction of docker if it fails to start/install properly with some feedback. 👍

GiteaMirror commented

2026-04-16 08:21:59 -05:00

@realrolfje commented on GitHub (Oct 10, 2025):

Vanilla install on a clean aws EC2 instance fails to install Docker:

Steps I needed to do manually to install that on EC2:

sudo yum install docker
sudo systemctl enable docker
sudo systemctl start docker
sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
sudo chmod +x  /usr/local/bin/docker-compose

After that, still on a vanilla EC2, I ran into CrowdSec fails with the defaults:

[+] Running 1/1
 ✘ Network pangolin  Error                                                                                                                                       0.0s
failed to create network pangolin: Error response from daemon: could not find an available, non-overlapping IPv6 address pool among the defaults to assign to the network
Error installing CrowdSec: failed to start containers: failed to start containers: exit status 1

@realrolfje commented on GitHub (Oct 10, 2025): Vanilla install on a clean aws EC2 instance fails to install Docker: <img width="585" height="397" alt="Image" src="https://github.com/user-attachments/assets/908338bc-f765-402b-a438-60dc7c3aca44" /> Steps I needed to do manually to install that on EC2: ``` sudo yum install docker sudo systemctl enable docker sudo systemctl start docker sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose sudo chmod +x /usr/local/bin/docker-compose ``` After that, still on a vanilla EC2, I ran into CrowdSec fails with the defaults: ``` [+] Running 1/1 ✘ Network pangolin Error 0.0s failed to create network pangolin: Error response from daemon: could not find an available, non-overlapping IPv6 address pool among the defaults to assign to the network Error installing CrowdSec: failed to start containers: failed to start containers: exit status 1 ```

GiteaMirror referenced this issue

2026-04-16 08:51:31 -05:00

[GH-ISSUE #1637] OCID fails with Authentik - how to troubleshoot? #1966

GiteaMirror referenced this issue

2026-04-20 08:09:13 -05:00

[GH-ISSUE #1637] OCID fails with Authentik - how to troubleshoot? #3908

GiteaMirror referenced this issue

2026-04-25 15:41:07 -05:00

[GH-ISSUE #1637] OCID fails with Authentik - how to troubleshoot? #6762

GiteaMirror referenced this issue

2026-04-30 04:44:35 -05:00

[GH-ISSUE #1637] OCID fails with Authentik - how to troubleshoot? #8730