Weebo's Dev Images

This is a collection of images that I use in my Dev Env. In the past those images were stored in my personal registry, but now it's time to move them to github.

Images actively built

These images are built and pushed to ghcr.io/batleforc/weebodevimage on every push to main and every night.

Image	Base	Description
che-min-mise	ubuntu:26.04	Minimal tooling image (mise, kubectl, FiraCode, shell setup). Serves as the tools component in the sidecar devfiles and as the base for che-mise-pdm.
che-mise-pdm	che-min-mise	che-min-mise + Podman (rootless nested containers, containers.conf/registries.conf preconfigured).
che-vscode	quay.io/che-incubator/che-code	Eclipse Che VS Code editor with a custom volume entrypoint.
che-browser	ubuntu:26.04	Sidecar: headed Chrome behind Xvfb, viewable via noVNC (6080), with an nginx CDP proxy (9222) and webdriver (9515).
che-kubedock	ubuntu:26.04	Sidecar: kubedock — a Docker API that spins up containers as Kubernetes pods (2475).
che-lgtm	grafana/otel-lgtm	Sidecar: Grafana LGTM observability stack (Loki, Grafana, Tempo, Mimir + OTel collector).
che-mailpit	ubuntu:26.04	Sidecar: Mailpit SMTP testing server with web UI.
che-rustfs	ubuntu:26.04	Sidecar: RustFS S3-compatible object storage.

Each sidecar folder ships a devfile.yaml combining che-min-mise (tools) with the sidecar itself.

Disabled images

The following images are kept in the repo for reference but are no longer built (see disabled_images in versions.yaml): che-min, che-base, che-base-slim, che-golang, che-node, che-rust, che-polyglot, che-mise, che-ops.

Their last built tags remain available on ghcr.io but will not receive updates. Remove an entry from disabled_images to re-enable a build.

Development

• task render — regenerate Containerfile/devfile.yaml from templates and versions.yaml
• task lint — check that rendered files match their templates
• task build IMAGE=che-browser — build one image locally
• task build-all — build every active image in dependency order