Public | Automated Build

Last pushed: 2 years ago
Short Description
Containerized version of znc.
Full Description


ZNC is an advance IRC bouncer that support persistent connectivity. ZNC can
remain connected to channels while any IRC compatiable client can freely
disconnect/reconnect without fear of missing out in the conversation.

This subfolder contains all necessary files to build a Docker image for ZNC.


  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D


Before reporting your issue please try updating Docker to the latest version
and check if it resolves the issue. Refer to the Docker installation guide for instructions.

SELinux users should try disabling SELinux using the command setenforce 0 to see if it resolves the issue.

If the above recommendations do not help then report your issue along with the following information:

  • Output of the docker version and docker info commands
  • The docker run command or docker-compose.yml used to start the image. Mask out the sensitive bits.
  • Please state if you are using Boot2Docker, VirtualBox, etc.

Getting started


Docker Hub:

It is recommended you install directly from the Docker Hub.

The following command copies over a wrapper scrip that will create a container
named znc when executed. The wrapper script will ensure that the
container gets setup with the appropriate environment variables and volumes
each time it is executed.

Start the installation by issuing the following command from within a terminal:

docker run -it --rm -v /usr/local/bin:/target \
    hurricane/znc instl

Optionally, you can also install a systemd service file. Before installing the
systemd service file, you might want specify which user you wish the daemon to
run as, specifically if it differs from the user running the installation. You
can do this by reinstalling znc with the following command:

docker run -it --rm -v /usr/local/bin:/target -e "APP_USER=username" \
    hurricane/znc instl

If the user you specified does not have a valid home directory you will
probably want to specify an alternate location to store the znc
configuration and back logs like so:

docker run -it --rm -v /usr/local/bin:/target \
    -e "APP_USER=username" \
    -e "APP_CONFIG=/var/lib/znc" \
    hurricane/znc instl

Above, change the username to the name of the user you wish to run the daemon
as, and adjust /var/lib/znc to wherever it is you wish to store ZNC's
configuration. Please verify that $APP_USER is the owner of $APP_CONFIG.

Afterward, proceed with the service file installation:

docker run -it --rm -v /etc/systemd/system:/target \
   hurricane/znc instl service

If you installed the systemd service file, you can enable ZNC to automatically
start when the system boots by executing the following command:

sudo systemctl enable znc.service


Installation from GitHub is recommended only for the purposes of
troubleshooting and development. To install ZNC from GitHub execute the

git clone
cd docker-containers/znc
make instl

Additionally, you can install the systemd service file after executing the
above by issuing the following:

make service

Initial Configuration:

Once ZNC has been installed you can simply execute the binary from a terminal:


Upon the intial creation of the container it will create a random password for
the admin user. You can retrieve the password by executing the following:

docker logs znc

Please log into the web interface as soon as possible and create a new
administrative user named anything other than admin. Afterwards, delete the
original admin user.



If you have installed our systemd service file, you can update by
executing the following command:

sudo systemctl restart znc.service

Additionally you can update by:

docker exec znc update

Or by executing:

docker pull hurricane/znc
docker stop znc

Automatic Upgrades:

In order to have the container periodically check and upgrade the znc binary
one needs to add a crontab entry. Like

echo "0 2 * * * docker exec znc update" | sudo tee -a /var/spool/cron/crontabs/root


docker run -it --rm \
  --volume /usr/local/bin:/target \
  hurricane/znc uninstl

Shell Access

For debugging and maintenance purposes you may want access the containers
shell. If you are using Docker version 1.3.0 or higher you can access
a running containers shell by starting bash using docker exec:

docker exec -it znc bash


You can find the template for this container on GitHub. Located here.

unRAID Installation:

Please navigate to the Docker settings page on unRAID's Web-UI and under repositories add:

For more information on adding templates to unRAID please visit the unRAID forums.

Check the container logs the on first run to retrieve admin the admin password.

unRAID Automatic Upgrades:

On unRAID, execute the following to have the container periodically update
itself. Additionally, add the same line of code to your go file to make the
change persistent.

echo "0 2 * * * docker exec ZNC update" | sudo tee -a /var/spool/cron/crontabs/root

Technical information:

By default the image has been created to run with UID and GID 1000. If using
the automatic install method from Docker, the container is set to run with the
UID and GID of of the user executing the znc wrapper script. Additionally,
the wrapper script by default saves ZNC's configuration and settings in
a hidden sub folder in the executing user's home directory. Most default
settings can be adjusted by passing the appropriate environment variable. Here
is a list of any and all applicable environment variables that can be override
by the end user.

Environment Variables:

You may overwrite the default settings by passing the appropriate environment variable:

  • APP_USER - name of user to create within container for purposes of running ZNC, UID, GID are more important.
  • APP_UID - UID assigned to APP_USER upon creation.
  • APP_GID - GID assigned to APP_USER upon creation.
  • APP_CONFIG - the directory that should house ZNC's metadata and configuration.

Please read Docker documentation on environment variables for more information.


  • /config - Folder to store ZNC's configuration and settings.

Manual Run and Installation:

Of course you can always run docker image manually. Please be aware that if you
wish your data to remain persistent you need to provide a location for the
/config volume. For example,

docker run -d --net=host -v /*your_config_location*:/config \
                         -e TZ=America/Edmonton
                         --name=ZNC hurricane/znc

All the information mention previously regarding user UID and GID still applies
when executing a docker run command.


Code released under the MIT license.


@hurricanehrndz: <a href=""><img src="" alt="[paypal]" /></a>

Docker Pull Command