full image - Repost: Portainer is creating duplicate volumes when launching a stack in swarm (from Reddit.com, Portainer is creating duplicate volumes when launching a stack in swarm)
Mining:
Exchanges:
Donations:
Hi everyone, I've been looking everywhere for an answer to this but I can't seem to find one. I've got a swarm of 4 Orange Pi 3B SBCs with one manager and 3 worker nodes. All are running debian for ARM64. I have initialized the swarm and gotten Portainer installed with minimal problems.My intent is to keep all persistent data on my file server through a cifs share. I have created the required volumes with appropriate settings, and once the volumes have been created, I can see a test file in the volume when I browse within portainer.When I create a stack within Portainer, however, Portainer is adding one or more extra volumes under the same name but set up as local stores instead of the network share. Please see my example below for the compose file.version: '3'services: vikunja: image: vikunja/vikunja environment: VIKUNJA_SERVICE_PUBLICURL: http://192.168.0.38 VIKUNJA_DATABASE_HOST: db VIKUNJA_DATABASE_PASSWORD: ******** VIKUNJA_DATABASE_TYPE: mysql VIKUNJA_DATABASE_USER: vikunja VIKUNJA_DATABASE_DATABASE: vikunja VIKUNJA_SERVICE_JWTSECRET: ************* ports: - 3456:3456 volumes: - vikunja:/app/vikunja/files restart: unless-stopped db: image: mariadb:10 command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci environment: MYSQL_ROOT_PASSWORD: ******* MYSQL_USER: vikunja MYSQL_PASSWORD: ********** MYSQL_DATABASE: vikunja volumes: - vikunja_db:/var/lib/mysql restart: unless-stoppedvolumes: vikunja: external: true vikunja_db: external: trueAs far as I can tell, I'm doing everything per documentation but by default Portainer is putting the persistent data in the local volumes named vikunja and vikunja_db instead of the ones which point to the cifs share.I hope I'm just overlooking something simple.
Social Media Icons