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
2. Open your browser to `http://<dockerd host ip>:9000`
@@ -25,17 +25,35 @@ Bind mounting the Unix socket into the UI For Docker container is much more secu
25
25
26
26
By default UI For Docker connects to the Docker daemon with`/var/run/docker.sock`. For this to work you need to bind mount the unix socket into the container with `-v /var/run/docker.sock:/var/run/docker.sock`.
27
27
28
-
You can use the `-e` flag to change this socket:
28
+
You can use the `-H` flag to change this socket:
29
29
30
30
# Connect to a tcp socket:
31
-
$ docker run -d -p 9000:9000 --privileged uifd/ui-for-docker -e http://127.0.0.1:2375
31
+
$ docker run -d -p 9000:9000 --privileged uifd/ui-for-docker -H tcp://127.0.0.1:2375
32
32
33
33
### Change address/port UI For Docker is served on
34
34
UI For Docker listens on port 9000 by default. If you run UI For Docker inside a container then you can bind the container's internal port to any external address and port:
35
35
36
36
# Expose UI For Docker on 10.20.30.1:80
37
37
$ docker run -d -p 10.20.30.1:80:9000 --privileged -v /var/run/docker.sock:/var/run/docker.sock uifd/ui-for-docker
38
38
39
+
### Access a Docker engine protected via TLS
40
+
41
+
Ensure that you have access to the CA, the TLS certificate and the TLS key used to access your Docker engine.
42
+
43
+
These files will need to be named `ca.pem`, `cert.pem` and `key.pem` respectively. Store them somewhere on your disk and mount a volume containing these files inside the UI container:
0 commit comments