Docker (recommended)
--network host is required so the container can reach your BMCs directly on your local
network over UDP port 623 (the IPMI/RMCP+ port). Without host networking, the container
sits behind Docker’s NAT and cannot complete an IPMI session with your hardware.
Once the container is up, open http://<your-ip>:3000 and follow the setup wizard.
The published image lives on Docker Hub at
hub.docker.com/r/ipmideck/ipmideck.
The image is coming soon — the command above is the exact command you will run once
it is published.
pip
ipmitool to be installed on the host — ipmideck shells out to
ipmitool for every IPMI operation. Install it from your distribution’s package manager
first (for example apt install ipmitool or dnf install ipmitool).
Where ipmideck stores data
ipmideck writes its configuration and database under a data directory:- Docker:
/datainside the container (the image setsIPMIDECK_DATA_DIR=/data; persist it with a volume). - pip on Linux:
/databy default — setIPMIDECK_DATA_DIRto relocate it. - pip on Windows:
./data, relative to the directory you runipmideckfrom.
IPMIDECK_DATA_DIR environment
variable. This directory holds config.yaml, the SQLite database, and the encryption key
file used to protect your stored BMC credentials. See Configuration and
Running ipmideck for details.
Next steps
- Configuration — tune ports, polling intervals, and retention.
- Supported Hardware — confirm your BMC is covered.
- Troubleshooting — connection and IPMI errors.