Self-host phpIPAM with Levelrail
An open source IP address management app for tracking subnets, addresses, VLANs and devices, backed by MariaDB. Finish the database install from the first page with the generated root password.
- Authorphpipam
- LicenceGPL-3.0-or-later
- Memory512 MiB
- Services2
How to self-host phpIPAM
-
Pull the images
2 images are pulled on your server.
Show images
mariadb:11.8.9phpipam/phpipam-www:v1.9.0
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 5 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the page, choose automatic database installation, enter root and the generated database root password, then set the admin password.
phpIPAM requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-or-later, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then phpIPAM. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the phpIPAM docs page.
Deploy phpIPAM your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy phpIPAM from the CLI
levelrail-cli templates install phpipam --name my-phpipam Deploy phpIPAM with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/phpipam/install \
-d '{
"name": "my-phpipam"
}' phpIPAM configuration
phpIPAM services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | mariadb:11.8.9 | none | mariadb_data -> /var/lib/mysql |
| phpipam | phpipam/phpipam-www:v1.9.0 | 80 | none |
phpIPAM environment variables
| Variable | Service | Value |
|---|---|---|
| MYSQL_ROOT_PASSWORD | db | Generated at deploy |
| IPAM_DATABASE_HOST | phpipam | Preset by the template |
| IPAM_DATABASE_NAME | phpipam | Preset by the template |
| IPAM_DATABASE_PASS | phpipam | Generated at deploy |
| IPAM_DATABASE_USER | phpipam | Preset by the template |
| IPAM_DATABASE_WEBHOST | phpipam | Preset by the template |
| TZ | phpipam | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: mariadb_data -> /var/lib/mysql
phpIPAM FAQ
How much memory does phpIPAM need?
The catalog lists about 512 MiB of memory for phpIPAM across its 2 services.
Does phpIPAM run on arm64?
For phpIPAM, arm64 support is not confirmed; amd64 is unknown.
What licence is phpIPAM under?
phpIPAM is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.
Does phpIPAM need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does phpIPAM bundle?
The template includes MySQL, running as its own service.
Which ports does phpIPAM use?
phpIPAM listens on port 80 inside the stack.
Where does phpIPAM keep its data?
In a named volume: mariadb_data mounted at /var/lib/mysql.
Can I deploy phpIPAM on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for phpIPAM, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image mariadb:11.8.9, phpipam/phpipam-www:v1.9.0 is what you deploy there.