louislam / dockge

A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager

Home Page:https://dockge.kuma.pet

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Improper docker run -> compose conversion for volumes

lockheed opened this issue Β· comments

⚠️ Please verify that this bug has NOT been reported before.

  • I checked and didn't find similar issue

πŸ›‘οΈ Security Policy

Description

I was trying to move portainer into dockge by converting this command
docker run -d -p 8000:8000 -p 9443:9443 --name=portainer --restart=always --network frontend -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:sts
and the result for volumes section is wrong:

volumes:
portainer_data: {}

As a result, the existing volume is not connected to the container and all portainer data is not available.

What it should be is:

volumes:
portainer_data:
external: true
name: portainer_data

as per doing the same operation on https://www.composerize.com

πŸ‘Ÿ Reproduction steps

As above

πŸ‘€ Expected behavior

mounted existing volume

πŸ˜“ Actual Behavior

not

Dockge Version

latest

πŸ’» Operating System and Arch

Arch x64

🌐 Browser

Firefox

πŸ‹ Docker Version

latest

🟩 NodeJS Version

No response

πŸ“ Relevant log output

No response