Repository navigation
|
Docman looks just great and seems to be th eperfect solution (hostorically I've been managing docker compose files by hand, through scripts, though Ansible, through Portainer, through th einitial dockge, then forks of dockge, ouf.). I have files that are layed out, from the host perspective, in I wanted to plug this to dockman and naturally I set services:
dockman:
image: ghcr.io/ra341/dockman:latest
environment:
- DOCKMAN_COMPOSE_ROOT=/etc/docker/compose
volumes:
- /etc/docker/compose:/etc/docker/compose
- config:/config
- /var/run/docker.sock:/var/run/docker.sock
restart: always
labels:
- traefik.enable=true
- traefik.http.routers.dockman.rule=Host(`dockman.XXX.eu`)
- traefik.http.services.dockman.loadbalancer.server.url=http://dockman:8866
volumes:
config: {}
networks:
default:
name: proxy
external: trueWhat I see in the web interface is: 
When creating a new stack I see this: 
On the other hand, the file swas created successfully: A |
Replies: 4 comments 10 replies
|
Ah, I just relized that the compose file is not the standard But nevertheless existing |
|
The name of the file shouldn't matter Are there any special/hidden chars in the filename Also check that the permissions are correct, Dockman runs as 1000:1000 by default. If your files are roo,t it might not be able to read You can change this by setting, |
No, I tried with
The files are with a high number UID, available to Also the error is |
|
Any logs in docker Also the logs in the browser |
|
Sorry, I forgot to mention the logs, obviously
No, even in debug mode
Not much more either: |
|
I am not sure at this point Some more troubleshooting tips
can you show me the raw request in the browser network tab, the url will be https://dockman.XXX.eu/api/protected/local/file/load/compose%2Fbichon%2Fcompose.yaml?download=false |
|
There is progress! So this must be something with the reverse proxy and dockman checking incoming URLs (?) Where does land on the backend? (https://github.com/RA341/dockman/blob/0e95abb1d92960a2f4a6707e36345ba0fe70d7b3/ui/src/context/file-context.tsx#L225C9-L225C100) |
|
Same here, I have the same issue. Works well if I run dockman and reach it directly with the IP address of my server, but doesn't behind traefik. |
Do you also use an authentication middleware (authelia, keycloak, ...)? |
|
I have enabled them currently And dockman Auth is disabled currently as I'm testing on a lab infra |
|
After searching a bit more, apparently traefik blocks urls with encoded paths Which is what this endpoint is using https://www.reddit.com/r/selfhosted/comments/1pkvs0f/traefik_364_breaks_renovate/ Try this config |
|
Yeah I still get the same error :/ |
|
OK Got it fixed!!! Was due to the version of Traefik. Thanks for the help |
I had a look at the release notes and there was a regression following the fix of a CVE. 3.6.7 restored the previous behaviour. Upgrading to 3.6.7 was enough. Thank you @elian0072 for the solution - this was really bad luch to have landed on that specifc regression in Traefik. @RA341 thanks for the follow-up, the issue was in the edge router. Thanks for your great software, I am going to ditch dockge to use dockman. I have two FR :) |
OK Got it fixed!!! Was due to the version of Traefik.
So my way of making it work, use Traefik traefik:v3.6.7
Allow encoded slash as explained by @wsw70 in your config (through lables or your dynamic config file)
I have defined DOCKMAN_MACHINE_ADDR pointing to my dockman url (ex: dockman.example.com)
I do pass the variables GID and PUID to the id of the user of my session which isn't 1000.
And it did the trick :)
Thanks for the help