New Portainer install agent issue

[jet438]

Ask a Question!

I just put up Portainer for a three node swarm. While checking the service with "sudo docker service ps portainer_agent" I'm seeing that the worker nodes are rejecting with an error of "invalid mount config for type…". How do I fix that? ....or is this intended?
For my other containers (standalone apps) I'm using a mount point which is actually an NFS directory on a file server. I read the documentation indicating that portainer would create a persistent volume within the docker data files so I'm not really sure how to correct it. My nodes do not share any shared file system created by me

[Nick-Portainer]

Can you please share how you deployed your swarm environment? Please share as much info around this and your environment so I can help troubleshoot

[jet438]

I actually figured that one out this morning. I moved Docker's data directory to an SSD drive. Apparently the folders for network and volumes need to remain in /var/lib/docker. Now that part works fine.
What I'm now having issues with is connecting remotely. I have two sets of Docker. One is a swarm and the other is not. Nextcloud's documentation says that, although possible, they don't advise deploying NC on a swarm. That said I built a separate swarm to play with and deploy Kasm workspaces.
Right now I have separate portainers for my NC and swarm machines. I've tried combining them to just one with two environments but every time I put the following in the daemon.json file the docker service fails. Can't for the life of me figure out what I'm doing wrong.

{
"data-root": "/media/cloud/dockerdata",
"hosts": ["unix:///var/run/docker.sock", "tcp://0.0.0.0:2375"]
}