Note: this is the "per-architecture" repository for the arm32v5 builds of the znc official image -- for more information, see "Architectures other than amd64?" in the official images documentation and "An image's source changed in Git, now what?" in the official images FAQ.
Maintained by:
the ZNC Community
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Dockerfile linksWARNING: THIS IMAGE IS NOT SUPPORTED ON THE arm32v5 ARCHITECTURE
Where to file issues:
https://github.com/znc/znc-docker/issues
Supported architectures: (more info)
amd64, arm32v6, arm64v8
Published image artifact details:
repo-info repo's repos/znc/ directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo's library/znc label
official-images repo's library/znc file (history)
Source of this description:
docs repo's znc/ directory (history)
ZNC is an IRC network bouncer (BNC). It can detach the client from the actual IRC server, and also from selected channels. Multiple clients from different locations can connect to a single ZNC account simultaneously and therefore appear under the same nickname on IRC.
ZNC in this image stores its configuration in /znc-data. If you have existing configuration, you can reuse it with -v $HOME/.znc:/znc-data. Alternatively, you can create a new config in a volume or in a local dir. The examples below assumes a volume named znc-cfg.
$ docker run -it -v znc-cfg:/znc-data arm32v5/znc --makeconf
To run ZNC:
$ docker run -p 12345:12345 -v znc-cfg:/znc-data arm32v5/znc
The port (12345 in the example above) should match the port you used during --makeconf. Note that 6667 and 6697 are often blocked by web browsers, and therefore are not recommended for ZNC.
If you use any external module, put the .cpp, .py or .pm file to /znc-data/modules (you may need to create that directory).
This image contains the latest released version. If you want the bleeding edge (unstable) version, it's at zncbouncer/znc-git.
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info repository's znc/ directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.