Skip to content

About

RHEL's ubi10 containers are a strong fit for stable, foundational environments.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

37 Commits

Folders and files

Repository files navigation

Not Your Ordinary Devcontainer

I got tired of using ordinary devcontainers. Here's what I wanted to build instead:

1. AI as a First-Class Citizen

We sandbox our agents and control their context via clever mounting. Every image except base mounts a portable-agents volume at /var/llms, so agent credentials, plugins, and history survive rebuilds.

The agents themselves are Dev Container Features, so each project picks one, two, or all of them:

{
    "image": "faangbait/workspaces:django",
    "features": {
        "ghcr.io/faangbait/dnf-features/claude:1": {
            "pluginMarketplaces": "anthropics/claude-plugins-official",
            "plugins": "chrome-devtools-mcp@claude-plugins-official frontend-design@claude-plugins-official playwright@claude-plugins-official"
        },
        "ghcr.io/faangbait/dnf-features/grok:1": {}
    }
}

2. Built on UBI10 from Red Hat

If you're unfamiliar, the Universal Base Image 10 is what they (and their customers) put at the core of any containerized workload.

That makes them incredibly stable. EOL for this base image is in 2035.

3. Layered for Fast Builds

Each layer of the Containerfile is decoupled from the other layers, so that only a few layers need to be rebuilt when things change. More details in ADR003.md and docs/mermaid.md.

make build builds the default images (base, agents, python, django, devops); make fullbuild adds typescript, rust, and golang. Builds run four at a time (-j4), and since the images share BuildKit layers, most of the work is deduplicated. Each image's log is held until its build finishes, so output stays readable. On a machine short on memory, run make -j1 build.

Contributing

I tend to go the extra few steps up front to strip out excess personal/opinionated config, but there's still plenty of opinions included. I'm willing to accept any pull request that maintains my defaults.

More Information

See docs/ADR*.md

Less Opinionated Alternative

By default, these devcontainers are highly opinionated to prefer AWS, to the point of rewriting the ssh command to proxy through ssm. To disable this behavior and use ssh like normal, include this in devcontainer.json:

"postCreateCommand": "mkdir -p ~/.ssh && { grep -qs 'ProxyCommand none' ~/.ssh/config || printf '\\n# Undo image SSM defaults\\nHost *\\n ProxyCommand none\\n User %s\\n' \"$(id -un)\" >> ~/.ssh/config; } && chmod 600 ~/.ssh/config",

About

RHEL's ubi10 containers are a strong fit for stable, foundational environments.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages