Resolved an issue on use of the 'Restrict Proc Mount Types' Kubernetes pod security constraint where the restriction was not being applied. Resolved an issue in the Kubernetes Advanced deployment screen, where a backend panic could occur when deploying some invalid YAML manifests. Updated the link...
Provide feedback We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly Cancel Create saved search Sign in Sign up {...
fruit:veto_appledouble = no fruit:wipe_intentionally_left_blank_rfork = yes[samba] path = /mount/ browsable = yes writable = yes available = yes read only = no guest ok = no veto files = /.apdisk/.DS_Store/.TemporaryItems/.Trashes/desktop.ini/ehthumbs.db/Network Trash Folder/Temporary...
Fixed issue where adding a service should be prevented when no volume has been selected for a volume mapping:https://github.com/portainer/portainer/issues/4651 Fixed issue with the MountType and nfsvers when creating NFS4 volumes:https://github.com/portainer/portainer/issues/4729 Edge: Show the...
In this example, each Edge device the stack was deployed to would mount their specific device (based on the Portainer Edge ID) folder from within the config directory of the Git repository to the /my-device-config folder in the container. If you deploy your stack to a device that does no...
If the socket bind mount is correct, that means that the data folder bind mount is incorrect, are you sure that the /data folder is available the hosts where Portainer should be deployed and that Docker can actually writes to these folders? Also, try the following bind mount: --mount typ...
Introduced validation to prevent adding a mount with nothing filled to and exiting service Fixed issue in service creation, switching to bind mode from volume mode with a volume selected fills the host field with {object Object}Stacks ...
Introduced validation to prevent adding a mount with nothing filled to and exiting service Fixed issue in service creation, switching to bind mode from volume mode with a volume selected fills the host field with {object Object} Stacks ...