boolve@alien.topOPBtoPortainer•random/missing additional path when creating the stackEnglish
1·
11 months agoI did. Usually I never use a relative way to describe the patch. But thanks for suggesting it.
I did. Usually I never use a relative way to describe the patch. But thanks for suggesting it.
Can you expand on what you mean by that. Thanks
Sure I know about environment variables but as you spot it I think those anchors do not go through Portainer. Mostly my errors comes as a configuration file missing in etc. this is the reason why I’m asking if anyone has succeeded before I carry on spending another evening with it.
Have you tried exactly on this compose? It doesn’t work. And I have used Portainer for a couple of years.
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.