You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 compose example:
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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 compose
example: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