Portainer, Simplicity without Compromize...

183 readers

6 users here now

Portainer is the definitive open source UI for simplifying Kubernetes, Docker, Swarm, Edge and ACI container management. Build, manage, and deploy containers in your environment quickly and easily. No more CLI, no more mistakes, just simple, fast configuration in a graphical UI, built on a trusted open source platform. Please note, this is not an official support channel. For CE, please head to Git Hub or our Slack channel. For Portainer Business, please refer to https://support.portainer.io/

founded 4 years ago

MODERATORS

[email protected]

Best (correct) way to use local mapped volumes with Portainer Stacks (lemmy.world)

submitted 1 week ago by [email protected] to c/[email protected]

0 comments fedilink hide all child comments

Hi all, In my current setup, I run many different containers each with its own compose folder. My main use case is mapping data volumes to a subfolder of where the compose file is located (as in './mydata:/root/app/data') instead of using the default docker volume folder.

What's the correct way of doing this in a portainer stack? I'd like to avoid using an absolute path (either direct or in a variable) for each container if possible...

TIA

no comments (yet)

sorted by: hot top controversial new old

there doesn't seem to be anything here