What the person above is suggesting: * https://pi.dev/ * https://omp.sh/ Personally I also think that OpenCode is nice, their CLI version is enjoyable and their desktop/web version is mostly okay: * https://opencode.ai/. - Source: Hacker News / 7 days ago

I wired it into OpenCode, an open-source coding harness similar to Claude Code and Codex. I'm using an OpenCode Zen key and a Gemini key, and together, these give me access to multiple SOTA models for free, without touching a separate dashboard for each provider. - Source: dev.to / 17 days ago

I drove it from my coding-agent with a handful of commands. - Source: dev.to / 19 days ago

Https://pi.dev/docs/latest/providers#openai-codex is specific that it "Requires ChatGPT Plus or Pro subscription". https://opencode.ai are also both specific that it's for "Plus/Pro" subscriptions. Is there some link where you saw free tier Codex use in non-official apps is allowed by OpenAI? (I have used the free tier in the official Codex app, but as you said, labs can have different rules for official vs... - Source: Hacker News / 23 days ago

Https://opencode.ai/ OpenCode was the first agent harness I used, and I have always like it. You can configure a wide variety of providers, but it's open source and has a number of core contributors. The other opinionated option is Pi (the Pi agent harness). This is a great lightweight option and also supports a number of providers. You can also use local model servers. - Source: Hacker News / about 2 months ago

Modern Docker releases use BuildKit, an efficient builder developed by Docker, whereas Podman uses Red Hat's Buildah. However, both solutions output OCI-compliant images, so there's no practical difference between the two for standard build workflows. - Source: dev.to / about 1 year ago

I suspect that the GP was really asking "why not use a different tool", like buildah , buildpacks , nix ,. - Source: Hacker News / over 1 year ago

Buildah specializes in building OCI-compliant container images, offering a more granular and secure approach to image creation compared to traditional Dockerfile builds. - Source: dev.to / over 1 year ago

Lockdown your Dockerized build environments --- Because privileged mode is insecure, you should restrict your CI/CD environments to known users and projects. If this isn't feasible, then instead of using Docker, you could try using a standalone image builder like Buildah to eliminate the risk. Alternatively, configuring rootless Docker-in-Docker can mitigate some --- but not all --- of the security concerns... - Source: dev.to / about 2 years ago

In my experience, not using docker to build docker images is a good idea. E.g. buildah[0] with chroot isolation can build images in a GitLab pipeline, where docker would fail. It can still use the same Dockerfile though. If you want to get rid of your Dockerfiles anyway, nix can also build docker images[1] with all the added benefits of nix (reproducibility, efficient building and caching, automatic layering,... - Source: Hacker News / almost 3 years ago