Dockerized version of NIPAP [web frontend], the world's best IPAM tool.
919
Docker stack-ready images for nipapd
This image starts the nipap web interface on port 8080. A valid (trusted) user
account on a running nipapd middleware is required.
| Variable | Description | Default |
|---|---|---|
NIPAPD_HOST | hostname of the nipapd to connect to | - |
NIPAPD_PORT | port on the nipapd to connect to | 1337 |
NIPAPD_USERNAME | username to bind to nipapd with | - |
NIPAPD_PASSWORD | password to bind to nipapd with | - |
WWW_USERNAME | name of account to create (def. auth) | - |
WWW_PASSWORD | password of account (def. auth) | - |
AUTH_BACKEND | name of auth backend to be used | local |
AUTH_CACHE | auth cache timeout in seconds | 3600 |
WWW_USERNAME, WWW_PASSWORD, NIPAPD_USERNAME and NIPAPD_PASSWORD all have
a corresponding var_FILE environment variable that can be used to retrieve the
desired contents from a file, rather than directly passing it via the docker
command line.
For use with docker secrets, one could use
NIPAPD_PASSWORD_FILE=/run/secrets/nipap-pw for example.
Every executable file in /nipap/docker-init.d/ will be executed to allow further
customization of the container during startup. Beware that these are executed on
every container start, so they should be idempotent.
If your script must run only once, you should use a marker file within a persisted
volume like /etc/nipap/.
If AUTH_DEFAULT is set to f[alse], 0, n[o] or skip, the default config
for authentication will not be generated (and nipap-passwd will not be executed
by the entrypoint script).
Instead, you have to setup the backend yourself using the following syntax:
AUTH_BACKEND_x_y will create [auth.backends.x], if it does not exist and set
the y key there to the corresponding value of the variable. Beware that x must
not contain an underscore!
Variable names ending in _FILE will be treated the same way as described in Secret
support.
A few examples:
AUTH_BACKEND_local_db_path will set db_path in auth.backends.localAUTH_BACKEND_remote_ro_group will set ro_group in auth.backends.remoteAUTH_BACKEND_remote_search_password_FILE will set search_password in
auth.backends.remote to the contents of the file
$AUTH_BACKEND_remote_search_password_FILEAlso, beware that a local auth backend is always required for nipapd to start. Thus
the image also has the following two environment variables set by default:
AUTH_BACKEND_local_type = SqliteAuthAUTH_BACKEND_local_db_path = /etc/nipap/local_auth.dbContent type
Image
Digest
Size
368.7 MB
Last updated
over 7 years ago
docker pull jonasprogrammer/nipap-www