Augment Code Reviews

runc Reviews

Augment Code mentions (4)

• Launch HN: Nia (YC S25) – Give better context to coding agents

  Congrats. From my experience, Augment (https://augmentcode.com) is best in class for AI code context. How does this compare? - Source: Hacker News / 9 months ago

• I've tried all (46 😵‍💫) AI Coding Agents & IDEs

  Augment Code Works in VS Code and JetBrains. Built for coders. Can execute code, run terminal, find issues, and analyze the code. Find performance optimization ideas in production. - Source: dev.to / about 1 year ago

• Claude 3.7 Sonnet and Claude Code

  At Augment (https://augmentcode.com) we were one of the partner who tested 3.7 pre-launch. And it has been a pretty significant increase in quality and code understanding. Happy to answer some questions FYI, We use Claude 3.7 has part of the new features we are shipping around Code Agent & more. - Source: Hacker News / over 1 year ago

• Chat is a bad UI pattern for development tools

  IMHO, I would agree with you. I think chat is a nice intermediary evolution between the CLI (that we use every day) and whatever comes next. I work at Augment (https://augmentcode.com), which, surprise surprise, is an AI coding assistant. We think about the new modality required to interact with code and AI on a daily basis. Beside increase productivity (and happiness, as you don't have to do mundane tasks like... - Source: Hacker News / over 1 year ago

runc mentions (11)

• Setup multi node kubernetes cluster using kubeadm

  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

• Comparing 3 Docker container runtimes - Runc, gVisor and Kata Containers

  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

• You run containers, not dockers - Discussing Docker variants, components and versioning

  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

• US Cybersecurity: The Urgent Need for Memory Safety in Software Products

  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

• Why did the Krustlet project die?

  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