Open deubert-it opened 5 months ago
We've seen issues in the past with network storage being used for the portainer_data
volume - our database (BoltDB) doesn't appear to play well with all filesystems. Unfortunately there's no easy fix for this, and while we're looking at possible alternative database options for the future I don't have any sort of ETA on when that might be implemented.
Before you start please confirm the following.
Problem Description
We are using 9pshare backed docker volumes and portainer won't start.
Maybe this is related to virtio/9pshare not supporting every needed filesystem feature like locking?
Expected Behavior
We would like to use 9pshare backed docker volumes, which work in other places, with portainer as well.
Actual Behavior
The portainer container crashes/crashloops because it can't "open" the store.
We tested it with both existing files in the volume and an empty volume, same behaviour.
Steps to Reproduce
Our docker swarm is running on debian qemu virtual machines. The virtual machines use virtio/9pshare mounts to access a folder on the kvm host. The folder is a cephfs mount.
qemu config for 9pshare from the host side:
in the debian vm we use this to consume the 9pshare mount and mount it in the same place:
now in our docker-compose/docker stack config, our volume just looks like this:
We use docker volumes similar to this with other containers without problems (i.e. min.io).
Portainer logs or screenshots
Portainer version
2.19.4
Portainer Edition
Community Edition (CE)
Platform and Version
Docker Swarm 25.0.3
OS and Architecture
debian 12
Browser
No response
What command did you use to deploy Portainer?
No response
Additional Information
No response