nano-wallet
100K+
The LinuxServer.io team brings you another container release featuring:
Find us at:
Nano-wallet is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies. With ultrafast transactions and zero fees on a secure, green and decentralized network, this makes Nano ideal for everyday transactions.
This container is a simple nginx wrapper for the light wallet located here. You will need to pass a valid RPC host when accessing this container.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/nano-wallet:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-<version tag> |
| arm64 | ✅ | arm64v8-<version tag> |
| armhf | ✅ | arm32v7-<version tag> |
This container requires a Nano RPC endpoint to communicate with whether a public network or your own, see here for more information.
Simply access the container at the URL:
http://localhost/#/THE_IP_OR_HOSTNAME_OF_RPC_ENDPOINT
Here are some example snippets to help you get started creating a container.
---
version: "2.1"
services:
nano-wallet:
image: lscr.io/linuxserver/nano-wallet:latest
container_name: nano-wallet
ports:
- 80:80
restart: unless-stopped
docker run -d \
--name=nano-wallet \
-p 80:80 \
--restart unless-stopped \
lscr.io/linuxserver/nano-wallet:latest
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function |
|---|---|
-p 80 | Webserver port |
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
-e FILE__PASSWORD=/run/secrets/mysecretpassword
Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
docker exec -it nano-wallet /bin/bashdocker logs -f nano-walletdocker inspect -f '{{ index .Config.Labels "build_version" }}' nano-walletdocker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nano-wallet:latestMost of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
docker-compose pull
docker-compose pull nano-walletdocker-compose up -d
docker-compose up -d nano-walletdocker image prunedocker pull lscr.io/linuxserver/nano-wallet:latestdocker stop nano-walletdocker rm nano-wallet/config folder and settings will be preserved)docker image prunePull the latest image at its tag and replace it with the same env variables in one run:
docker run --rm \
-v /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower \
--run-once nano-wallet
You can also remove the old dangling images: docker image prune
Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-nano-wallet.git
cd docker-nano-wallet
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/nano-wallet:latest .
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
docker run --rm --privileged multiarch/qemu-user-static:register --reset
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
Content type
Image
Digest
Size
11.3 MB
Last updated
over 3 years ago
Requires Docker Desktop 4.37.1 or later.
Pulls:
1
Feb 2 to Feb 8