File README.md of Package micro-fips-image
# SUSE Linux BCI Micro 16.0 FIPS-140-3 mode: Suitable for deploying static binaries  [-Level_4-Green)](https://documentation.suse.com/sbp/security/html/SBP-SLSA4/) [](https://documentation.suse.com/container/all/html/Container-guide/index.html#container-verify) ## Description The `bci-micro` image includes the RPM database, but not the RPM package manager. This means that the image is smaller than `bci-minimal`. The primary use case for the image is deploying static binaries produced externally or during multi-stage builds. This base container image is configured with FIPS mode enabled by default, but it **does not** include any certified binaries. ## Usage As there is no straightforward way to install additional dependencies inside the container image, we recommend deploying a project using the `bci-micro` image only when the final build artifact bundles all dependencies and needs no further installation of packages. Example using a Go application: ```Dockerfile FROM registry.suse.com/bci/golang:stable as build WORKDIR /app RUN go install github.com/go-training/helloworld@latest # Create an image to bundle the app FROM registry.suse.com/bci/bci-micro-fips:16.0 COPY --from=build /go/bin/helloworld /usr/local/bin/helloworld CMD ["/usr/local/bin/helloworld"] ``` ## Licensing `SPDX-License-Identifier: MIT` This documentation and the build recipe are licensed as MIT. The container itself contains various software components under various open source licenses listed in the associated Software Bill of Materials (SBOM). This image is based on [SUSE Linux BCI](https://opensource.suse.com/bci/), a stable and redistributable foundation for software innovation. SUSE Linux BCI is enterprise-ready, and it comes with an option for support. See the [SUSE Linux BCI EULA](https://www.suse.com/licensing/eula/#bci) for further information.
