Docker images generated and published automatically from the Nimbus-eth1 CI, by a GitHub action, whenever a new release is tagged in Git.
These images are simply the contents of Nimbus-eth1 release tarballs inside a "debian:bullseye-slim" image, running under a user imaginatively named "user", with UID:GID of 1000:1000.
The unpacked archive is in "/home/user/nimbus-eth1" which is also the default WORKDIR. The default ENTRYPOINT is the binary itself: "/home/user/nimbus-eth1/build/nimbus".
You need to create an external data directory and mount it as a volume inside the container, with the mounting point being "/home/user/nimbus-eth1/build/data".
mkdir data
docker run -it --rm -v ${PWD}/data:/home/user/nimbus-eth1/build/data statusim/nimbus-eth1:amd64-latest [nimbus args here]
Better yet, use docker-compose, with one of the example configuration files as a base for your custom configuration:
mkdir data
docker-compose -f docker-compose-example1.yml up --quiet-pull --no-color --detach
The rather voluminous logging is done on stdout, so you might want to change the system-wide Docker logging defaults (dumping everything in "/var/lib/docker/containers/CONTAINER_ID/CONTAINER_ID-json.log") to something like "syslog". Make sure there's some log rotation system in use and the intervals make sense for these large logs.
Content type
Image
Digest
sha256:bd7ecdd24…
Size
311.6 MB
Last updated
about 2 hours ago
docker pull statusim/nimbus-eth1:master-7cd9269