Creating stack from Git fail with relative path volumes & rootless docker about portainer

[adriengivry]

@BakasuraRCE Thanks for the answer! To be honest I just ditched rootless docker, and now I have 0 issue with Portainer, everything is so smooth 😅
Rootless docker is just a pain in the a** to deal with when using Portainer, half of the features are broken. Anyway, problem solved for me 😁

[adriengivry]

Workaround:

# Adding the rootless Docker user to the docker group
sudo usermod -aG docker $USER
newgrp docker

# Changing docker.sock permissions
sudo chmod 666 /var/run/docker.sock

# Restarting docker
systemctl restart docker

However this fixed this issue, I'm a bit concerned about this chmod 666 on the docker.sock, it might have side effects and be a security issue. Thoughts?

Edit: Even though this allows the stack to be deployed, the stack display no container, and the containers are created with sudo docker instead of docker.

[adriengivry]

I've disabled rootfull docker, and trying to create a stack from a Git repository with relative path triggers this error:

an error occurred while running unpacker container with exit code 255: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? 

It seems like even though portainer is ran with rootless docker, it still tries to access rootfull docker to create this stack.
Maybe a bug in the relative path implementation using the sudo prefix where it shouldn't?

[BakasuraRCE]

Don't ask me why this works, I don't understand the reason, but it does:

Create a symbolic link to the volume of your portainer on your host server

$ ln -s /home/USER_HERE/.local/share/docker/volumes/portainer-prod_portainer_data/_data /data

Now try to deploy but do not enable relative paths

This works well temporarily, but in an environment multi-node we need Portainer to solve it