kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Documentation
LinuxServer-CI
rodzic
e0fdce7f78
commit
3ef6208f4c
|
|
@ -1,6 +1,9 @@
|
|||
---
|
||||
title: nano
|
||||
---
|
||||
<!-- DO NOT EDIT THIS FILE MANUALLY -->
|
||||
<!-- Please read the https://github.com/linuxserver/docker-nano/blob/master/.github/CONTRIBUTING.md -->
|
||||
|
||||
# [linuxserver/nano](https://github.com/linuxserver/docker-nano)
|
||||
|
||||
[](https://github.com/linuxserver/docker-nano)
|
||||
|
|
@ -15,7 +18,6 @@ title: nano
|
|||
|
||||
[Nano](https://nano.org/) 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.
|
||||
|
||||
|
||||
## 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](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
|
||||
|
|
@ -38,132 +40,6 @@ This image provides various versions that are available via tags. `latest` tag u
|
|||
| latest | Stable Nano releases |
|
||||
| beta | Beta Nano releases |
|
||||
|
||||
## Usage
|
||||
|
||||
Here are some example snippets to help you get started creating a container from this image.
|
||||
|
||||
### docker-compose ([recommended](https://docs.linuxserver.io/general/docker-compose))
|
||||
|
||||
Compatible with docker-compose v2 schemas.
|
||||
|
||||
```yaml
|
||||
---
|
||||
version: "2.1"
|
||||
services:
|
||||
nano:
|
||||
image: ghcr.io/linuxserver/nano
|
||||
container_name: nano
|
||||
environment:
|
||||
- PUID=1000
|
||||
- PGID=1000
|
||||
- TZ=Europe/London
|
||||
- PEER_HOST=localhost #optional
|
||||
- LIVE_GENESIS_PUB=GENESIS_PUBLIC #optional
|
||||
- LIVE_GENESIS_ACCOUNT=nano_xxxxxx #optional
|
||||
- LIVE_GENESIS_WORK=WORK_FOR_BLOCK #optional
|
||||
- LIVE_GENESIS_SIG=BLOCK_SIGNATURE #optional
|
||||
- CLI_OPTIONS=--config node.enable_voting=true #optional
|
||||
- LMDB_BOOTSTRAP_URL=http://example.com/Nano_64_version_20.7z #optional
|
||||
volumes:
|
||||
- /path/to/data:/config
|
||||
ports:
|
||||
- 8075:8075
|
||||
- 7076:3000
|
||||
- 7077:3001
|
||||
restart: unless-stopped
|
||||
```
|
||||
|
||||
### docker cli
|
||||
|
||||
```
|
||||
docker run -d \
|
||||
--name=nano \
|
||||
-e PUID=1000 \
|
||||
-e PGID=1000 \
|
||||
-e TZ=Europe/London \
|
||||
-e PEER_HOST=localhost `#optional` \
|
||||
-e LIVE_GENESIS_PUB=GENESIS_PUBLIC `#optional` \
|
||||
-e LIVE_GENESIS_ACCOUNT=nano_xxxxxx `#optional` \
|
||||
-e LIVE_GENESIS_WORK=WORK_FOR_BLOCK `#optional` \
|
||||
-e LIVE_GENESIS_SIG=BLOCK_SIGNATURE `#optional` \
|
||||
-e CLI_OPTIONS=--config node.enable_voting=true `#optional` \
|
||||
-e LMDB_BOOTSTRAP_URL=http://example.com/Nano_64_version_20.7z `#optional` \
|
||||
-p 8075:8075 \
|
||||
-p 7076:3000 \
|
||||
-p 7077:3001 \
|
||||
-v /path/to/data:/config \
|
||||
--restart unless-stopped \
|
||||
ghcr.io/linuxserver/nano
|
||||
```
|
||||
|
||||
|
||||
## 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`)
|
||||
|
||||
| Parameter | Function |
|
||||
| :----: | --- |
|
||||
| `8075` | Nano communication port |
|
||||
| `3000` | RPC interface filtered through a proxy |
|
||||
| `3001` | Https RPC interface filtered through a proxy |
|
||||
|
||||
|
||||
### Environment Variables (`-e`)
|
||||
|
||||
| Env | Function |
|
||||
| :----: | --- |
|
||||
| `PUID=1000` | for UserID - see below for explanation |
|
||||
| `PGID=1000` | for GroupID - see below for explanation |
|
||||
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London |
|
||||
| `PEER_HOST=localhost` | Default peer host (can be overidden with an array by command line options) |
|
||||
| `LIVE_GENESIS_PUB=GENESIS_PUBLIC` | Genesis block public key |
|
||||
| `LIVE_GENESIS_ACCOUNT=nano_xxxxxx` | Genesis block account |
|
||||
| `LIVE_GENESIS_WORK=WORK_FOR_BLOCK` | Genesis block proof of work |
|
||||
| `LIVE_GENESIS_SIG=BLOCK_SIGNATURE` | Genesis block signature |
|
||||
| `CLI_OPTIONS=--config node.enable_voting=true` | Node run command cli args |
|
||||
| `LMDB_BOOTSTRAP_URL=http://example.com/Nano_64_version_20.7z` | HTTP/HTTPS endpoint to download a 7z file with the data.ldb to bootstrap to this node |
|
||||
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
| Volume | Function |
|
||||
| :----: | --- |
|
||||
| `/config` | Main storage for config and blockchain |
|
||||
|
||||
|
||||
|
||||
## 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](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
||||
|
||||
|
||||
## User / Group Identifiers
|
||||
|
||||
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
|
||||
|
||||
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
|
||||
|
||||
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
|
||||
|
||||
```
|
||||
$ id username
|
||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||
```
|
||||
|
||||
## Application Setup
|
||||
|
||||
### Your Genesis account
|
||||
|
|
@ -351,13 +227,133 @@ docker create \
|
|||
linuxserver/nano
|
||||
```
|
||||
|
||||
## Usage
|
||||
|
||||
Here are some example snippets to help you get started creating a container from this image.
|
||||
|
||||
### docker-compose ([recommended](https://docs.linuxserver.io/general/docker-compose))
|
||||
|
||||
Compatible with docker-compose v2 schemas.
|
||||
|
||||
```yaml
|
||||
---
|
||||
version: "2.1"
|
||||
services:
|
||||
nano:
|
||||
image: ghcr.io/linuxserver/nano
|
||||
container_name: nano
|
||||
environment:
|
||||
- PUID=1000
|
||||
- PGID=1000
|
||||
- TZ=Europe/London
|
||||
- PEER_HOST=localhost #optional
|
||||
- LIVE_GENESIS_PUB=GENESIS_PUBLIC #optional
|
||||
- LIVE_GENESIS_ACCOUNT=nano_xxxxxx #optional
|
||||
- LIVE_GENESIS_WORK=WORK_FOR_BLOCK #optional
|
||||
- LIVE_GENESIS_SIG=BLOCK_SIGNATURE #optional
|
||||
- CLI_OPTIONS=--config node.enable_voting=true #optional
|
||||
- LMDB_BOOTSTRAP_URL=http://example.com/Nano_64_version_20.7z #optional
|
||||
volumes:
|
||||
- /path/to/data:/config
|
||||
ports:
|
||||
- 8075:8075
|
||||
- 7076:3000
|
||||
- 7077:3001
|
||||
restart: unless-stopped
|
||||
```
|
||||
|
||||
### docker cli
|
||||
|
||||
```bash
|
||||
docker run -d \
|
||||
--name=nano \
|
||||
-e PUID=1000 \
|
||||
-e PGID=1000 \
|
||||
-e TZ=Europe/London \
|
||||
-e PEER_HOST=localhost `#optional` \
|
||||
-e LIVE_GENESIS_PUB=GENESIS_PUBLIC `#optional` \
|
||||
-e LIVE_GENESIS_ACCOUNT=nano_xxxxxx `#optional` \
|
||||
-e LIVE_GENESIS_WORK=WORK_FOR_BLOCK `#optional` \
|
||||
-e LIVE_GENESIS_SIG=BLOCK_SIGNATURE `#optional` \
|
||||
-e CLI_OPTIONS=--config node.enable_voting=true `#optional` \
|
||||
-e LMDB_BOOTSTRAP_URL=http://example.com/Nano_64_version_20.7z `#optional` \
|
||||
-p 8075:8075 \
|
||||
-p 7076:3000 \
|
||||
-p 7077:3001 \
|
||||
-v /path/to/data:/config \
|
||||
--restart unless-stopped \
|
||||
ghcr.io/linuxserver/nano
|
||||
```
|
||||
|
||||
## 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`)
|
||||
|
||||
| Parameter | Function |
|
||||
| :----: | --- |
|
||||
| `8075` | Nano communication port |
|
||||
| `3000` | RPC interface filtered through a proxy |
|
||||
| `3001` | Https RPC interface filtered through a proxy |
|
||||
|
||||
### Environment Variables (`-e`)
|
||||
|
||||
| Env | Function |
|
||||
| :----: | --- |
|
||||
| `PUID=1000` | for UserID - see below for explanation |
|
||||
| `PGID=1000` | for GroupID - see below for explanation |
|
||||
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London |
|
||||
| `PEER_HOST=localhost` | Default peer host (can be overidden with an array by command line options) |
|
||||
| `LIVE_GENESIS_PUB=GENESIS_PUBLIC` | Genesis block public key |
|
||||
| `LIVE_GENESIS_ACCOUNT=nano_xxxxxx` | Genesis block account |
|
||||
| `LIVE_GENESIS_WORK=WORK_FOR_BLOCK` | Genesis block proof of work |
|
||||
| `LIVE_GENESIS_SIG=BLOCK_SIGNATURE` | Genesis block signature |
|
||||
| `CLI_OPTIONS=--config node.enable_voting=true` | Node run command cli args |
|
||||
| `LMDB_BOOTSTRAP_URL=http://example.com/Nano_64_version_20.7z` | HTTP/HTTPS endpoint to download a 7z file with the data.ldb to bootstrap to this node |
|
||||
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
| Volume | Function |
|
||||
| :----: | --- |
|
||||
| `/config` | Main storage for config and blockchain |
|
||||
|
||||
## Environment variables from files (Docker secrets)
|
||||
|
||||
You can set any environment variable from a file by using a special prepend `FILE__`.
|
||||
|
||||
As an example:
|
||||
|
||||
```bash
|
||||
-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](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
||||
|
||||
## User / Group Identifiers
|
||||
|
||||
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
|
||||
|
||||
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
|
||||
|
||||
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
|
||||
|
||||
```bash
|
||||
$ id username
|
||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||
```
|
||||
|
||||
## Docker Mods
|
||||
|
||||
[](https://mods.linuxserver.io/?mod=nano "view available mods for this container.") [](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
|
||||
|
||||
We publish various [Docker Mods](https://github.com/linuxserver/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:
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue