From 4e7fa6b4b9e6ac302fb7db3eba9ad29a08483e8a Mon Sep 17 00:00:00 2001 From: Simon L Date: Tue, 8 Nov 2022 19:29:49 +0100 Subject: [PATCH] Add explanation of the initial docker run command to the readme Signed-off-by: Simon L --- readme.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/readme.md b/readme.md index 742e0fec..74a6b60a 100644 --- a/readme.md +++ b/readme.md @@ -52,6 +52,21 @@ The following instructions are especially meant for Linux. For macOS see [this]( +
+ Explanation of the command + + - `sudo docker run` This command spins up a new docker container. + - `--name nextcloud-aio-mastercontainer` This is the name of the container and cannot be changed since mastercontainer updates would fail. + - `--restart always` This is the "restart policy". `Always` means that the container should get started always. See the docker documentation on further policies. + - `--publish 80:80` This means that port 80 of the container should get published on the host using port 80. It is used for getting valid certificates for the AIO interface if you want to use port 8443. It is not needed if you run AIO behind a reverse proxy and can get removed in that case as you can simply use port 8080 for the AIO interface then. + - `--publish 8080:8080` This means that port 8080 of the container should get published on the host using port 8080. This port is used for the AIO interface and uses a self-signed certificate by default. You can also use a different port like e.g. `--publish 8081:8080` if port 8080 should already be in use on your host. + - `--publish 8443:8443` This means that port 8443 of the container should get published on the host using port 8443. If you publish port 80 and 8443 to the public internet, you can access the AIO interface via this port with a valid certificate. It is not needed if you run AIO behind a reverse proxy and can get removed in that case as you can simply use port 8080 for the AIO interface then. + - `--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config` This means that the files that are created by the mastercontainer will be stored in a docker volume that is called `nextcloud_aio_mastercontainer`. This line is not allowed to be changed since built-in backups would fail later on. + - `--volume /var/run/docker.sock:/var/run/docker.sock:ro` The docker socket is mounted into the container which is used for spinning up all the other containers and for further features. It needs to be adjusted on Windows/macOS and on docker rootles. See the applicable documentation on this. If you dislike this, see https://github.com/nextcloud/all-in-one/discussions/500#discussioncomment-2740767 and the whole thread for options. + - `nextcloud/all-in-one:latest` or `nextcloud/all-in-one:latest-arm64` This is the docker container image that is used. See https://github.com/nextcloud/all-in-one/discussions/490 for why there are different images for the different CPU architectures. + - For further options like changing the location of Nextcloud's datadir or mounting some locatioins as external storage into the Nextcloud container, simply read through the readme and/or look at the docker-compose file: https://github.com/nextcloud/all-in-one/blob/main/docker-compose.yml +
+ 3. After the initial startup, you should be able to open the Nextcloud AIO Interface now on port 8080 of this server.
E.g. `https://ip.address.of.this.server:8080`

If your firewall/router has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via: