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
Copy file name to clipboardExpand all lines: README.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,9 @@ services:
39
39
image: ghcr.io/channinghe/labelgate:v0
40
40
container_name: labelgate
41
41
restart: unless-stopped
42
+
# use command "stat -c '%g' /var/run/docker.sock" to get the group id of the docker socket
43
+
group_add:
44
+
- "REPLACE_WITH_GROUP_ID"
42
45
volumes:
43
46
- /var/run/docker.sock:/var/run/docker.sock:ro
44
47
- ./labelgate-data:/app/config
@@ -48,6 +51,9 @@ services:
48
51
- LABELGATE_CLOUDFLARE_TUNNEL_ID
49
52
ports:
50
53
- "28111:8080"
54
+
# labelgate no need to connect to the network "cloudflared-network"
55
+
# Because Labelgate simply uses the Cloudflare API to create tunnel ingress rules or DNS records.
56
+
network_mode: bridge
51
57
52
58
cloudflared:
53
59
image: cloudflare/cloudflared:latest
@@ -68,6 +74,10 @@ services:
68
74
networks:
69
75
- cloudflared-network
70
76
77
+
# Create a network for the services you want to connect to cloudflared.
78
+
# This allows your Cloudflare tunnel to connect to services via their container_name within the "cloudflared-network" bridge, eliminating the need for port mapping.
79
+
# Consolidating all public services into a single network ensures they remain isolated from private services.
80
+
71
81
networks:
72
82
cloudflared-network:
73
83
```
@@ -84,9 +94,8 @@ That's it. Labelgate watches your containers and syncs labels to Cloudflare auto
84
94
-[x]**Tunnel Ingress** — Expose services through Cloudflare Tunnels without port forwarding
0 commit comments