Hi all,

I'm new to Unraid, but it' s a great product.

My question is regarding docker. I have created a custom network with docker network create traefik_proxy

I've installed my traefik as a yml (see below).

Sadly in the GUI, the network ID is displayed, but not the network name. Can I fix this?

 

this is my stack:

 

---
version: '3.7'

services:
  traefik:
    image: traefik:v2.11.0
    container_name: traefik
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro
      - /var/run/docker.sock:/var/run/docker.sock
      - ./config:/etc/traefik
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.traefik.rule=Host(`traefik.xxxxxxxxx.xx`) && (PathPrefix(`/api`) || PathPrefix(`/dashboard`))"
      - "traefik.http.routers.traefik.entrypoints=websecure"
      - "traefik.http.routers.traefik.tls.certresolver=default"
      - "traefik.http.routers.traefik.service=api@internal"
      - "traefik.http.routers.traefik.middlewares=auth@docker"
      - "traefik.http.middlewares.auth.basicauth.users=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    networks:
      - traefik_proxy
#      - default
    ports:
      - "80:80"
      - "443:443"
    restart: always

networks:
  traefik_proxy:
    name: traefik_proxy
    external: true

 

Edited February 27, 20242 yr by tescher

I’m having the same issue.

 

Were you able to resolve it? I'm facing the exact same issue. I do not know how to display the network name instead of its ID.

Thanks!

Sure didn’t. It’s not a deal breaker, just makes the ui look weird. It only stresses me out when I’m checking in on a docker issue so I haven’t spent too much time on it. 

If you only need to run one docker service (not a complex compose stack), you can do so by creating the container through Unraid UI (Add Container) or using the docker CLI. It worked for me; The network name is displayed correctly.
I wasn't able to achieve the same result through compose.

Edited March 10, 20242 yr by alozzi

That’s a work around that I’ve used before. I prefer using docker compose due to its portability but that’s a totally viable alternative.

looking for a solution to this as well.

+1 looking for a solution to this. I moved from Docker Compose Manager to Portainer and both are having the same issue. Spent too much time thinking I was doing something wrong myself.

What you are all seeing is a known issue with the way Dockerman displays networks for containers created via compose. There is an open PR for the unRAID webui to fix the issue but as of yet it is unmerged. https://github.com/unraid/webgui/pull/1616 Aside from patching the webui there is no convenient way to fix this.

@primeval_god thank you for the link and information. Hopefully it will be sorted out in the next update.