ubuntu/nifi repository overview

ubuntu/nifi is a rock for nifi maintained by Canonical⁠.

Apache NiFi 2.x packaged on Ubuntu with a Java 21 runtime, a pruned NAR set (23 of 119 bundles), a non-root runtime user, and Pebble as the entrypoint. Built from source and used as the workload image for the Charmed NiFi operator.

[Learn more about nifi⁠]

⁠Tags and Architectures

NOTE: These tags follow a specific naming convention that respects the concept of channels⁠.

⁠Get started

This rock's entrypoint is Pebble, a container-optimized init process that enables the orchestration of a collection of local service processes as an organized set.

[Learn more about Pebble⁠]

⁠Inspect

To view the Pebble services⁠ and checks⁠ defined in this rock:

docker run --rm ubuntu/nifi:2.10-26.04_edge plan

⁠Run

To run this rock, use any of the usual container runtimes, for example, docker:

docker run --name nifi-container \
    -p 8080:8080 \
    ubuntu/nifi:2.10-26.04_edge

Pebble (PID 1) launches the nifi service (nifi.sh run). The rock is configured for HTTP on port 8080 with anonymous access; NiFi self-bootstraps its sensitive-properties key on first start. Access the UI at http://localhost:8080/nifi⁠. (TLS termination and single-user authentication are added by the Charmed NiFi operator, not the standalone rock.)

⁠Get logs

To view the logs of the running container, run:

docker exec nifi-container pebble logs

Or, for a specific service:

docker exec nifi-container pebble logs <service>

⁠Monitor health checks

Rocks may have predefined health checks that you can list by running:

docker exec nifi-container pebble checks

The overall health of your container can be inspected via:

docker exec nifi-container pebble health

⁠Configuration

⁠Volumes

⁠Ports

[Report a bug⁠] [Contribute⁠]

Canonical is the provider of this container image. It is the user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within, as well as with Canonical’s IP Policy⁠.