|
|
|
@ -7,7 +7,12 @@ Running Zeronet in Docker container
|
|
|
|
|
Run
|
|
|
|
|
===
|
|
|
|
|
```
|
|
|
|
|
docker run -d --name zeronet -v zeronet_data:/data -p 43110:43110 -p 15441:15441 my/zeronet
|
|
|
|
|
docker run -d \
|
|
|
|
|
--name zeronet
|
|
|
|
|
-v zeronet_data:/data
|
|
|
|
|
-p 127.0.0.1:43110:43110
|
|
|
|
|
-p 15441:15441
|
|
|
|
|
my/zeronet
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Access
|
|
|
|
@ -19,14 +24,16 @@ http://127.0.0.1:43110
|
|
|
|
|
Additional notes
|
|
|
|
|
================
|
|
|
|
|
|
|
|
|
|
If you already have your Web browser running in a container (e.g. Firefox in
|
|
|
|
|
the `firefox_net` network), then you can run Zeronet container in the
|
|
|
|
|
following way
|
|
|
|
|
If you are running your Web browser in the container, then you need to make
|
|
|
|
|
sure both containers are on the same network in order to access the ZeroNet WebUI.
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
docker run -d --name zeronet -v zeronet_data:/data --net firefox_net -p 15441:15441 my/zeronet
|
|
|
|
|
docker network connect glue
|
|
|
|
|
docker network connect glue chrome
|
|
|
|
|
docker network connect glue zeronet
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
With docker-compose it is even simpler
|
|
|
|
|
Running zeronet with docker-compose:
|
|
|
|
|
```
|
|
|
|
|
docker-compose up -d
|
|
|
|
|
```
|
|
|
|
|