You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: When launching a folder inside the Stack folder with uppercase letters, the folder is recognized but remains inactive. If I try to start it through the UI, a second, active, non-managed entry is created, while the original entry (with uppercase letters) remains inactive.
The inactive container still shows the logs for that container.
P.S. Thank you to the developers for the excellent work on Dockge! Keep it up, and I hope this report helps in improving the software.
👟 Reproduction steps
Create or rename a folder inside the Stack folder with uppercase letters.
Start the folder via the UI or CLI.
Observe that the folder remains inactive, and a new active entry is created with only Lowercase letters.
👀 Expected behavior
The folder with uppercase letters should become active when started, without creating a second inactive entry.
😓 Actual Behavior
The folder with uppercase letters remains inactive, while a second, active, non-managed entry is created.
Temporary Workaround: Renaming the folder (changing all cases to lowercase) resolves the issue and the folder becomes active. On the picture I renamed File RustDesk to rustdesk in the cli. After that it became active.
Dockge Version
1.4.2
💻 Operating System and Arch
Ubuntu 24.04.2 LTS x64 (headless)
🌐 Browser
135.0 (64-Bit) for Ubuntu (Desktop)
🐋 Docker Version
Docker Engine 27.5.1 |
🟩 NodeJS Version
none
📝 Relevant log output
The following log is the same for all containers with capitalized letters:
2025-02-14T19:36:46Z [GETSERVICESTATUSLIST] ERROR: Error: Process exited with code 15
at ChildProcess.done (/app/node_modules/.pnpm/[email protected]/node_modules/promisify-child-process/index.cjs:70:19)
at ChildProcess.emit (node:events:514:28)
at ChildProcess.emit (node:domain:489:12)
at maybeClose (node:internal/child_process:1091:16)
at ChildProcess._handle.onexit (node:internal/child_process:302:5) {
code: 15,
signal: null,
stdout: '',
stderr: "validating /container/compose/Ollama/docker-compose.yml: name Does not match pattern '^[a-z0-9][a-z0-9_-]*$'\n"
The text was updated successfully, but these errors were encountered:
🛡️ Security Policy
Description
Description: When launching a folder inside the Stack folder with uppercase letters, the folder is recognized but remains inactive. If I try to start it through the UI, a second, active, non-managed entry is created, while the original entry (with uppercase letters) remains inactive.
The inactive container still shows the logs for that container.
P.S. Thank you to the developers for the excellent work on Dockge! Keep it up, and I hope this report helps in improving the software.
👟 Reproduction steps
👀 Expected behavior
The folder with uppercase letters should become active when started, without creating a second inactive entry.
😓 Actual Behavior
The folder with uppercase letters remains inactive, while a second, active, non-managed entry is created.
Temporary Workaround: Renaming the folder (changing all cases to lowercase) resolves the issue and the folder becomes active. On the picture I renamed File RustDesk to rustdesk in the cli. After that it became active.
Dockge Version
1.4.2
💻 Operating System and Arch
Ubuntu 24.04.2 LTS x64 (headless)
🌐 Browser
135.0 (64-Bit) for Ubuntu (Desktop)
🐋 Docker Version
Docker Engine 27.5.1 |
🟩 NodeJS Version
none
📝 Relevant log output
The text was updated successfully, but these errors were encountered: