mirror of
https://github.com/louislam/dockge.git
synced 2026-03-03 02:06:55 -05:00
Bind Mount Volume Translated Incorrectly From Docker Run #44
Labels
No labels
bug
feature-request
help
help wanted
invalid-format
need-reproduce-steps
question
security
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dockge-louislam#44
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MeCJay12 on GitHub (Nov 27, 2023).
⚠️ Please verify that this bug has NOT been reported before.
🛡️ Security Policy
Description
From the home page, this docker run command was entered into the converstion tool:
This was the output when trying to deploy the stack:
It seems like src and dst are incorrect and I was able to fix it by chnaging to source and target respectively.
👟 Reproduction steps
From the home page, enter this docker run command into the converstion tool:
👀 Expected behavior
The next Deploy button should launch the container successfully.
😓 Actual Behavior
Dockge Version
1.2.0
💻 Operating System and Arch
Ubuntu 22.04 x64
🌐 Browser
Chrome 119.0.6045.160 (Official Build) (64-bit)
🐋 Docker Version
No response
🟩 NodeJS Version
Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1
📝 Relevant log output
No response
@louislam commented on GitHub (Nov 28, 2023):
The correct one should be this. Will transfer the issue to https://github.com/composerize/composerize
@MeCJay12 commented on GitHub (Nov 28, 2023):
I noticed that if I set the type to volume it would not work at all in this form. I had to use the src:dst format for volume type volumes.
I'm opened this bug for
A little later on I found that bind mounts that are read only also convert wrong. I can open a new bug for it but I think it would be easy to fix at once. They come through as
readonly: nullwhen they should beread_only: true.