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

For kubeadm , kubetlet , kubectl should same version package in this lab I used v1.31 to have 1.31.7 References: Https://kubernetes.io/docs/reference/networking/ports-and-protocols/ Https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ Https://github.com/opencontainers/runc/releases/... - Source: dev.to / over 1 year ago

Previously I wrote about the multiple variants of Docker and also the dependencies behind the Docker daemon. One of the dependencies was the container runtime called runc. That is what creates the usual containers we are all familiar with. When you use Docker, this is the default runtime, which is understandable since it was started by Docker, Inc. - Source: dev.to / almost 2 years ago

Now we have dockerd which uses containerd, but containerd will not create containers directly. It needs a runtime and the default runtime is runc, but that can be changed. Containerd actually doesn't have to know the parameters of the runtime. There is a shim process between containerd and runc, so containerd knows the parameters of the shim, and the shim knows the parameters of runc or other runtimes. - Source: dev.to / almost 2 years ago

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / almost 3 years ago

Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 3 years ago