MISP Docker Lifecycle Manager

A non-invasive lifecycle manager for official MISP/misp-docker single-server Docker deployments.

This is an independent community project. It is not part of, endorsed by, certified by, sponsored by, or supported by the MISP project, CIRCL, or the upstream MISP maintainers. Read project origin and transparency for the non-affiliation, naming, validation, and AI-assisted development model.

Important — Release channels

Channel	Version	Meaning
Latest published	v1.4.1	Newest normal SemVer release; documentation/hosted-docs patch with exact-tag compatibility evidence
Latest validated	v1.4.1	Newest immutable release tag that passed the full compatibility matrix

Install and report the immutable SemVer tag. .release-channels.json is the machine-readable source; mutable stable and latest Git tags are intentionally not used.

Current VERSION value on main: 1.4.1.

The manager installs, configures, validates, updates, backs up, restores, and safely removes a supported deployment while leaving /opt/misp-docker as a normal official upstream checkout. It does not fork or replace MISP, and it is not a Kubernetes, high-availability, or multi-node orchestration layer.

Start with your task

For the current hosted reader experience, start at the verified Read the Docs site: misp-docker-lifecycle-manager.readthedocs.io. The repository-local links below remain the versioned/offline source of truth for exact branches and tags.

I want to…	Read this
choose the right path	docs/README.md
check whether my deployment is supported	docs/support-matrix.md
install and verify for the first time	docs/getting-started.md
follow normal lifecycle operations	docs/operator-guide.md and docs/monitoring.md
deploy behind a reverse proxy	docs/production-deployment.md
update safely	docs/upgrade-path.md
back up, restore, or recover	docs/backup-restore-and-rollback.md
troubleshoot or create a sanitized report	docs/troubleshooting.md and docs/sos-report.md
inspect validated compatibility evidence	docs/compatibility.md and docs/validation/matrix.md
contribute or maintain the project	docs/contribute-and-maintain.md

Quick test path

For the supported first-install workflow, read docs/getting-started.md. Use the latest validated-compatible release for deployments. Git is required before cloning:

sudo dnf install -y git
git clone https://github.com/Tuxmint-Open-Source/misp-docker-lifecycle-manager.git
cd misp-docker-lifecycle-manager
git checkout v1.4.1
sudo ./lifecycle/prepare-host-rocky.sh
sudo ./lifecycle/install.sh \
  --install-dir /opt/misp-docker \
  --upstream-ref master \
  --base-url https://misp.example.com \
  --admin-email admin@example.com \
  --admin-org ExampleOrg \
  --timezone Europe/Zurich \
  --exposure reverse-proxy

Then verify the deployment:

sudo ./lifecycle/doctor.sh --install-dir /opt/misp-docker
sudo ./lifecycle/login-check.sh --install-dir /opt/misp-docker

For production, recovery, updates, and limitations, use the linked guides rather than this abbreviated path. The default reverse-proxy path binds to loopback. A proxy on another host requires the explicit bind and source-restricted Docker-aware firewall procedure in the production deployment guide. The lifecycle manager does not modify the host firewall.

Validated compatibility

manager release/ref × official MISP Docker component set = status

The latest published and latest validated release is v1.4.1, a documentation/hosted-docs patch release that passed exact-tag and published-artifact validation for MISP core v2.5.44, modules v3.0.9, and guard v1.2. See compatibility, the current validation report, and the evidence archive.

Policy and project links

• Security reports: SECURITY.md
• Contributions: CONTRIBUTING.md
• Quality gates: QA.md
• Project identity: ASSET-LICENSE.md and brand assets
• Project origin and transparency: docs/project-origin-and-transparency.md
• Release history: CHANGELOG.md

Repository-local documentation remains the versioned and offline source of truth. The hosted latest documentation renders the current main branch. Older release tags before the MkDocs/Read the Docs foundation, including v1.4.0, should be read from the repository tag rather than expected to have hosted release-tag pages.

Read the Docs release-tag documentation starts with the first release tag that contains the MkDocs/Read the Docs foundation. Do not move or rewrite old release tags to make hosted pages build. Keep the hosted project root on latest until a post-foundation release tag is active, built, and verified as the RTD stable version.