Dockman no start UI 8866

[cerede2000]

I'm having a problem with Dockman versions higher than 1.0.2.

Even with a clean container in the log, the container never goes past the stage: DBG ../core/internal/git/service.go:125 > Got tree status

Here's the compose I'm using:

name: dockman
services:
  dockman:
    container_name: dockman
    image: ghcr.io/ra341/dockman:latest
    environment:
      - DOCKMAN_COMPOSE_ROOT=/stacks
      - DOCKMAN_LOG_LEVEL=debug
      - DOCKMAN_LOG_VERBOSE=true
    volumes:
      - /server/stacks/dockman/config:/config
      - /var/run/docker.sock:/var/run/docker.sock
      - /server/stacks:/stacks
    ports:
      - "8866:8866"
    restart: always

Here's what it looks like:

Another point I don't understand is that the container systematically uses an IP address of 192.168.48.2, even though I don't specify anything anywhere.

Why doesn't it use a standard 172.0.0 address?

Thanks :)

[RA341]

Your compose is incorrect

Don't store application data in the compose root its bad practice and the cause of your problem

You should move all container generated files, like databases, and other application data, outside of the compose root

See: https://github.com/RA341/dockman?tab=readme-ov-file#staging_lag

name: dockman
services:
  dockman:
    container_name: dockman
    image: ghcr.io/ra341/dockman:latest
    environment:
      - DOCKMAN_COMPOSE_ROOT=/stacks
      - DOCKMAN_LOG_LEVEL=debug
      - DOCKMAN_LOG_VERBOSE=true
    volumes:
      # - /server/stacks/dockman/config:/config <-- don't do this
      - /server/dockerdata/dockman/config:/config # <-- store outside of compose root 
      - /var/run/docker.sock:/var/run/docker.sock
      - /stacks:/stacks #<-- all paths must be absolute and same 
    ports:
      - "8866:8866"
    restart: always

/server/stacks -> /stacks

or the opposite if you want /server/stacks to be the path

name: dockman
services:
  dockman:
    container_name: dockman
    image: ghcr.io/ra341/dockman:latest
    environment:
      - DOCKMAN_COMPOSE_ROOT=/server/stacks
      - DOCKMAN_LOG_LEVEL=debug
      - DOCKMAN_LOG_VERBOSE=true
    volumes:
      - /server/stacks/dockman/config:/config
      - /var/run/docker.sock:/var/run/docker.sock
      - /server/stacks:/server/stacks #<-- all paths must be absolute and same 
    ports:
      - "8866:8866"
    restart: always

ip issue

For your ip issue I am not sure why it's happening

I built that so that I can have direct links to my containers by clicking thoer ports,

It works by pinging cloudflare dns and checks the address used

for containers it should be as you said 172.x.x.x

Maybe something in your docker network config

[cerede2000]

I'm going to release this.

But why did it work in 1.0.2 and later with higher versions?

I used Dockge before and had no problems, the same with Portainer, by the way.

I find Dockman much more convenient for managing my composes, but if I have to modify the entire container tree, I might get discouraged :(

[RA341]

Unlike portainer and dockge, The key difference is that dockman uses git to track your compose configs

V1.1 added multihost support which uses git branching under the hood, it needs to add and then branch off which is causing the issue

I working on a workaround for this issue, but thats a wip

[cerede2000]

To test, I created a new root stack /server/tempstack with only Dockman in it, and it works.

Dockman starts correctly and I can clearly see my containers running.

This is clearly a problem with the other elements present in the stack folders alongside the compose folder.

However, this is unfortunate; in v1.0.2, I appreciated the ability to edit my configuration files present in the stack folder directly from Dockman.

[RA341]

You still can do this, it only applies to container-generated data. Simple config files are fine

See

#43 (comment)

for how to layout your directories, it might be a pain but it will allow you to seperate your configs from your container data

[cerede2000]

I've redone my entire container tree.

Dockman is launched!