​​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​​

​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.

Supported Architectures

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling ghcr.io/linuxserver/nano-wallet 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:

Application Setup

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​

Usage

Here are some example snippets to help you get started creating a container from this image.

docker-compose (recommended)

Compatible with docker-compose v2 schemas.

---
version: "2.1"
services:
  nano-wallet:
    image: ghcr.io/linuxserver/nano-wallet
    container_name: nano-wallet
    ports:
      - 80:80
    restart: unless-stopped

docker cli

docker run -d \
  --name=nano-wallet \
  -p 80:80 \
  --restart unless-stopped \
  ghcr.io/linuxserver/nano-wallet

Parameters

Docker 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.

Ports (-p)

Environment Variables (-e)

Volume Mappings (-v)

Environment variables from files (Docker secrets)

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.

Umask for running applications

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.

Docker Mods

​​​ ​​​

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.

Support Info

• Shell access whilst the container is running:

  • docker exec -it nano-wallet /bin/bash

• To monitor the logs of the container in realtime:

  • docker logs -f nano-wallet

• Container version number

  • docker inspect -f '{{ index .Config.Labels "build_version" }}' nano-wallet

• Image version number

  • docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/nano-wallet

Versions

• 01.06.20: - Rebasing to alpine 3.12.

• 23.05.20: - Initial Release.