zebra/docker
Gustavo Valverde cdb9efdb27
fix(docker): allow the `zebra` user access to relevant dirs (#8817)
* fix(docker): allow the `zebra` user access to relevant dirs

When runnning a Zebra node using Docker without a privileged user, you won't be able to modify some files and directories, not even the ones in the current directory, as the `zebra` user has no permission to `/`.

The best way to solve this is making the `/opt/zebrad` the current `WORKDIR`. This also requires moving the `entrypoint.sh` from the root `/` directory to `/etc/zebrad` as this directory is used to save configuration, and other files.

An `APP_HOME` ARG is used as not all platforms where a Docker container is deployed allows writting permissions to the `/opt` directory. This allow some users to re-build the image with a custom `WORKDIR`

* fix(docker): allow starting the container without a `zebrad` command

As `gosu` is just required and available in our `runtime` image, trying to run `docker run -it --rm  --name tests -t zfnd/zebra:<pr> /bin/bash` in other stages will fail, as `gosu` is not available.
2024-08-29 19:57:17 +00:00
..
zcash-lightwalletd ref(build)!: use official lightwallted image for CI (#8323) 2024-02-29 15:50:50 +00:00
.env feat(docker): allow users to use Zebra + LWD with persistent states (#8215) 2024-02-01 21:54:17 +00:00
Dockerfile fix(docker): allow the `zebra` user access to relevant dirs (#8817) 2024-08-29 19:57:17 +00:00
docker-compose.lwd.yml feat(docker): allow users to use Zebra + LWD with persistent states (#8215) 2024-02-01 21:54:17 +00:00
docker-compose.test.yml
docker-compose.yml fix(docker): set log rotation to avoid docker bugs (#8269) 2024-02-20 10:40:38 +00:00
entrypoint.sh fix(docker): allow the `zebra` user access to relevant dirs (#8817) 2024-08-29 19:57:17 +00:00
test.env feat(docker): allow users to use Zebra + LWD with persistent states (#8215) 2024-02-01 21:54:17 +00:00