Portainer

28 readers

0 users here now

Portainer Community Edition is a lightweight service delivery platform for containerized applications that can be used to manage Docker, Swarm, Kubernetes and ACI environments.

founded 1 year ago

MODERATORS

[email protected]

random/missing additional path when creating the stack (alien.top)

submitted 11 months ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Hi,
With Portainer on Debian. I'm trying to create a stack from the git repo and the "additional path" function is required for me to add a file for the compose file. The problem is, that it is impossible to describe the patch. I have a file on the file system under `/mnt/lvol-docker/AppData/netbox/docker-compose.override.yml`, but when deploying the stack I have an error message saying that the directory or file does not exist. Weirdly enough my described path is appended with `/data/compose/78/b47e85ab3f2261021adf99ae9de2e9692fd674c3/mnt/lvol-docker/AppData/netbox/docker-compose.override.yml` but such a directory not exist. If I create such a directory structure and drop my file, then it looks like another random directory with a different number/name.

https://preview.redd.it/6qywnapaxd1c1.png?width=1594&format=png&auto=webp&s=db4eb1197769db29ebab7f8a98b2abc27cddf47d

What I'm missing here? Or maybe something else is involved? Any hints?

Thank you.

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 11 months ago (1 children)

Have you tried using the absolute path for the additional file instead of a relative one? It might help resolve the issue. Good luck!

[–] [email protected] 1 points 11 months ago

I did. Usually I never use a relative way to describe the patch. But thanks for suggesting it.

[–] [email protected] 1 points 11 months ago

I have no luck any ay on Portainer with netbox. I have cloned the repo , and edited the compose file an till having trouble with it. Seem that there is more external things going on behind the scenes not in the containers itself but externally until all is set. and this causes this problem. I have been stuck with the problem that dependencies between the containers fall as it seems to wait for wrong names but the compose file doesn't allow changing names. and because it does use there same containers it automatically renames spending the container name with the number 1 at the end. and seems that the dependents don't understand it. I'm not sure where to find the real logs but I; 'm reading from pop-up messages on Portainer.