I'm brand new to Unraid but familiar with Docker and Docker-Compose. The easiest route to executing `docker run` and Docker-Compose scripts seems to be installing Portainer. I clicked through the portainer search results on the Community Apps page to view the results from DockerHub, and installed the portainer-ce application.

 

However, when I access the admin console, I get this message on the Environment Wizard:

 

Quote

We could not connect your local environment to Portainer.
Please ensure your environment is correctly exposed.

 

In the logs for running docker application, I see this error message repeated:

 

Quote

2023/12/20 06:48PM WRN github.com/portainer/portainer/api/platform/platform.go:70 > failed to retrieve docker info | error="Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"

 

I haven't been able to find any information about how to fix this. I'm unsure what path the `docker.sock` socket lives at in Unraid, but even if I knew, I don't know how to send that volume to the `docker run` command via Unraid's Docker tab. I tried setting the portainer-ce application to "privileged" but that didn't help (I didn't think it would, but I'm just flipping switches at this point).

 

So where does the `docker.sock` socket live in Unraid, and how can I send this volume information to a Docker container in Unraid? Thanks in advance!

Are you aware that many containers can be installed from Community Applications without portainer or the command line? 

 

Have you installed any that way? 

 

https://docs.unraid.net/unraid-os/manual/docker-management/

50 minutes ago, magsol said:

easiest route to executing `docker run`

Community Applications is the easiest. If you install a container that way, you will see that it executes the docker run command using information you supply in the form on the Add Container.

 

Quote

Are you aware that many containers can be installed from Community Applications without portainer or the command line?

 

Yep! But a lot seem to come with built-in network configs that have to be changed; rather than try and guess which configuration options are exposed in the CA templates and which are hidden, I wanted to see if I could just spin up containers via docker run commands or docker-compose yamls; as I said, I'm more familiar with those.

 

Quote

 

Have you installed any that way? 

 

I have; nextcloud-aio and pi hole. In both cases I've run into some of the issues I mentioned about configuration ambiguity, hence I wanted to see if I could essentially strip out the UI entirely and build the configuration from scratch.

 

Quote

Community Applications is the easiest.

 

I completely agree, my problem is figuring out how Unraid works in this regard--it's the simplest, but that simplicity comes with hiding some details, like how to mount volumes within the container deployments. The portainer application I was running that couldn't find its local environment had that problem because it didn't have any mounts; the CA templates don't seem to have that problem (e.g. the CA PortainerCI mounts the volumes correctly), but I'm not entirely sure why, and critically: I haven't been able to figure out why. If someone could clarify how exactly the CA templates are built and how to specify the arbitrary options I am apparently missing, that would also fix my issues.

 

Thanks so much!

On the Add/Edit Container page, use slider at top to switch to Advanced View. Use Show more settings ... dropdown to see and edit things hidden by the templates, and Add another Path, Port, Variable, Label or Device if you need more.

 

Community Applications search also has Click Here To Get More Results From DockerHub for things that don't already have Unraid templates, and it will try to give you a starting template to work with.

A container you have already installed from the Add Container page stores its template on your flash drive in config/plugins/dockerMan/templates-user. They are XML you can examine.