CRITICAL: Correct dangerous claims about bootc production readiness
EXPERIMENTAL WARNINGS: - Add prominent warnings that bootc on Debian is HIGHLY EXPERIMENTAL - Clarify that NO reproducible bootc images exist yet - Warn that everything is still experimental and not production-ready - Add DO NOT use in production warnings throughout DEBIAN VERSION CORRECTIONS: - Use Debian Sid (unstable) for base image building (like Fedora rawhide) - Correct dangerous claims about 'tested' configurations - Mark all configurations as experimental, not tested - Remove false claims about production readiness SAFETY IMPROVEMENTS: - Add experimental warnings to all base image documentation - Clarify that bootc is not stable on Debian yet - Emphasize testing-only use on virtual machines - Remove misleading production recommendations This corrects dangerous misinformation that could lead to data loss and system instability in production environments.
This commit is contained in:
parent
49281ba325
commit
72155be8de
4 changed files with 40 additions and 16 deletions
|
|
@ -1,5 +1,14 @@
|
|||
# Create bootc base images without bootc
|
||||
|
||||
⚠️ **EXPERIMENTAL WARNING** ⚠️
|
||||
|
||||
**bootc on Debian is HIGHLY EXPERIMENTAL and NOT production-ready!**
|
||||
|
||||
- **No reproducible bootc images exist yet** - Everything is experimental
|
||||
- **Use only for testing** on virtual machines or test hardware
|
||||
- **Expect failures** - bootc is not stable on Debian
|
||||
- **DO NOT use in production** - Data loss and system instability possible
|
||||
|
||||
The bootc binary is unreliable under Debian as it's mainly developed for Fedora despite it aiming to be a distro agnostic tool.
|
||||
|
||||
In this doc we'll go over all the little things a base bootc needs to be considered a true bootc image.
|
||||
|
|
@ -312,7 +321,7 @@ echo "Example: podman build -f examples/nginx/Containerfile -t ${IMAGE_NAME}:ngi
|
|||
```dockerfile
|
||||
# Containerfile.wo-bootc - Build bootc base without bootc binary
|
||||
|
||||
FROM debian:trixie-slim
|
||||
FROM debian:sid-slim
|
||||
|
||||
# Install essential packages for bootc
|
||||
RUN apt update && apt install -y \
|
||||
|
|
@ -998,7 +1007,7 @@ CMD ["/lib/systemd/systemd"]
|
|||
|
||||
```dockerfile
|
||||
# examples/nginx/Containerfile.multistage
|
||||
FROM debian:trixie-slim as base
|
||||
FROM debian:sid-slim as base
|
||||
|
||||
# Install base packages
|
||||
RUN apt update && apt install -y \
|
||||
|
|
|
|||
|
|
@ -1,5 +1,14 @@
|
|||
# Building Base bootc Images
|
||||
|
||||
⚠️ **EXPERIMENTAL WARNING** ⚠️
|
||||
|
||||
**bootc on Debian is HIGHLY EXPERIMENTAL and NOT production-ready!**
|
||||
|
||||
- **No reproducible bootc images exist yet** - Everything is experimental
|
||||
- **Use only for testing** on virtual machines or test hardware
|
||||
- **Expect failures** - bootc is not stable on Debian
|
||||
- **DO NOT use in production** - Data loss and system instability possible
|
||||
|
||||
This document provides detailed instructions for creating base bootc images using two different approaches:
|
||||
|
||||
1. **Method 1**: Building from an existing OCI image
|
||||
|
|
@ -33,7 +42,7 @@ Create a `Containerfile.base`:
|
|||
|
||||
```dockerfile
|
||||
# Containerfile.base - Convert existing Debian image to bootc base
|
||||
FROM debian:trixie-slim
|
||||
FROM debian:sid-slim
|
||||
|
||||
# Install essential packages for bootc
|
||||
RUN apt update && apt install -y \
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue