Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improper docker run -> compose conversion for volumes #508

Open
2 tasks done
lockheed opened this issue May 1, 2024 · 0 comments
Open
2 tasks done

Improper docker run -> compose conversion for volumes #508

lockheed opened this issue May 1, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@lockheed
Copy link

lockheed commented May 1, 2024

⚠️ 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

@lockheed lockheed added the bug Something isn't working label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant