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

This stack is not managed by Dockge. #359

Closed
2 tasks done
markusglaetzner opened this issue Jan 10, 2024 · 2 comments
Closed
2 tasks done

This stack is not managed by Dockge. #359

markusglaetzner opened this issue Jan 10, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@markusglaetzner
Copy link

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

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

I get a "This stack is not managed by Dockge." for all projects in the defined stack-folder. I also get error messages in the dockge container-log every 5 min (see down below). After creating a new compose of an existing project (with the same name), I get full functionality in dockge - I do not know what happens here...

👟 Reproduction steps

I can reproduce this behavior when I restore my docker vm.

👀 Expected behavior

Full functionality on all stack-projects.

😓 Actual Behavior

All stack-projects are "greyed out" and when I click on one, I get message "This stack is not managed by Dockge."

Dockge Version

1.4.1

💻 Operating System and Arch

Debian 12

🌐 Browser

Firefox

🐋 Docker Version

24.0.7

🟩 NodeJS Version

18.19.0

📝 Relevant log output

2024-01-09T18:07:29+01:00 [GETSERVICESTATUSLIST] ERROR: Error: spawn docker ENOENT
    at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
    at __node_internal_errnoException (node:internal/errors:623:12)
    at ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:476:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
@markusglaetzner markusglaetzner added the bug Something isn't working label Jan 10, 2024
@ThreeTheOG
Copy link

What is your directory structure in your stacks directory?
Ex:
/opt/stacks
├── ollama
│   ├── compose.yaml
│   └── ollama
└── ollama-webui
└── compose.yaml

To list your tree, apt install tree, then run tree /opt/stacks -L 2.
(Update apt first and use your own dockge stacks directory if applicable.)

@louislam
Copy link
Owner

Docker spawn issue. Merge to #361.

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

3 participants