Replies: 1 comment
-
|
+1 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe
Lots of docker image maintainers use single-file volume mapping for their config files (filebrowser, timothyjmiller/cloudflare_ddns, so so many others). This prevents deploying these images using the direct Stacks editing feature of Portainer. There is no error, but the container cannot access the file.
Describe the solution you'd like
Allow single-file volume mapping to function as it does with
docker composeexample:Describe alternatives you've considered
I've attempted to start the stack once, stop it and go remove the directory Portainer created with the mapped filename, replacing it with the required file, then restart. But even in that instance, the container cannot access the file.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions