# Container Image Building

The process of creating container images, including building them from Dockerfiles or application packages such as JAR and WAR files.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Java4Shell: GitLab helps find and remediate a critical Java flaw

DevFeed: [Java4Shell: GitLab helps find and remediate a critical Java flaw](<https://devfeed.tech/articles/java4shell-gitlab-helps-find-and-remediate-a-critical-java-flaw-146875.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/java4shell-critical-java-flaw-how-gitlab-helps/>)

Author: Daniel Abeles

Published: 2026-11-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [x86](<https://devfeed.tech/topics/x86.md>)

Tags: [base64](<https://devfeed.tech/tags/base64.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cpus](<https://devfeed.tech/tags/cpus.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [java](<https://devfeed.tech/tags/java.md>), [java-flaw](<https://devfeed.tech/tags/java-flaw.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [november-17](<https://devfeed.tech/tags/november-17.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [optimized](<https://devfeed.tech/tags/optimized.md>), [option](<https://devfeed.tech/tags/option.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [security-labs](<https://devfeed.tech/tags/security-labs.md>), [security-research](<https://devfeed.tech/tags/security-research.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

Java4Shell is a memory corruption flaw in optimized Base64 decoding in recent x86-64 Java runtimes; researchers demonstrated unauthenticated remote code execution in several products' default configurations. The excerpt says GitLab assessed its own managed infrastructure as not exploitable, while proactively upgrading one component containing the affected bundle. It recommends upgrading Java runtimes from 17.0.6 onward to listed fixed builds or distribution patches; until then, `-XX:-UseBASE64Intrinsics` disables the vulnerable optimization with a slight performance cost and requires restarting Java processes. For discovery, it pairs static checks (package and optional binary container scanning, Orbit, and Java/Kotlin project filters) with runtime workload inventories, since each view can miss Java installations. It also outlines GitLab Duo agent workflows for proposing per-project fixes, with human review and merge.

### Source excerpt

GitLab has internally assessed the impact of Java4Shell, and concluded it is not exploitable in GitLab-managed infrastructure. Exploitation requires a specific combination of conditions, which we confirmed are not present in our production environment. A single component was found to contain the impacted bundle in its runtime environment, which we are proactively upgrading as a hardening measure. On November 17, 2026, OpenJDK, the project that most Java runtimes are built from, fixed a memory corruption flaw known as Java4Shell (CVE-2026-114938, CVSS 8.1) in the optimized java.util.Base64 decoding used on recent x86-64 CPUs. Web servers and frameworks routinely decode Base64 values from users, such as authentication headers and cookies, before the application sees the request. Researchers have demonstrated unauthenticated remote code execution in the default configurations of several widely used Java products. Upgrade Java to a fixed version now To mitigate this issue, upgrade every Java runtime from 17.0.6 onward, including unsupported releases such as Java 18 and 24, to a build based on OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1, or to your distribution's patched package. If you can't upgrade right away, turn off the vulnerable optimization with the -XX:-UseBASE64Intrinsics JVM option. Here are fixed builds and packages as of November 19: Vendor or distributionFixed build or packageOpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1Eclipse Temurin17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, 27.0.1.1+4Amazon Corretto17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4Azul Zulu17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1BellSoft Liberica17.0.21.1+5, 21.0.13.1+5, 25.0.5.1+5, 27.0.1.1+5SapMachine17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1Microsoft Build of OpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1Oracle Java SE 8 Performance Pack8u513-perf. Other Java 8 builds aren't affectedUbuntu 26.10, 26.04, 24.04, 22.04openjdk-17 17.0.21.1, openjdk-21 21.0.13.1, openjdk-25 25.0.5.1, and on 26.10

## Red Hat Enterprise Linux GitHub hosted runner images now generally available

DevFeed: [Red Hat Enterprise Linux GitHub hosted runner images now generally available](<https://devfeed.tech/articles/red-hat-enterprise-linux-github-hosted-runner-images-now-generally-available-139446.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/17/red-hat-enterprise-linux-github-hosted-runner-images-ga>)

Author: Louis Imershein, Mark Heslin

Published: 2026-11-17T14:01:36Z

Content type: release

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [rhel](<https://devfeed.tech/topics/rhel.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [automated](<https://devfeed.tech/tags/automated.md>), [avoid](<https://devfeed.tech/tags/avoid.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [but](<https://devfeed.tech/tags/but.md>), [cause](<https://devfeed.tech/tags/cause.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [containers](<https://devfeed.tech/tags/containers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-linux](<https://devfeed.tech/tags/enterprise-linux.md>), [github](<https://devfeed.tech/tags/github.md>), [hat](<https://devfeed.tech/tags/hat.md>), [hosted](<https://devfeed.tech/tags/hosted.md>), [images](<https://devfeed.tech/tags/images.md>), [linux](<https://devfeed.tech/tags/linux.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-enterprise](<https://devfeed.tech/tags/red-hat-enterprise.md>), [red-hat-enterprise-linux](<https://devfeed.tech/tags/red-hat-enterprise-linux.md>), [runner](<https://devfeed.tech/tags/runner.md>)

### AI overview

GitHub-hosted runner images for RHEL 9 and RHEL 10 are generally available for CI/CD teams using GitHub Enterprise Cloud or Server, enabling tests on the same Linux distribution as production. RHEL 9 is positioned for existing applications needing stability; RHEL 10 for newer projects, with GCC 14 and Python 3.12. These are minimal 64-bit Linux base images: Git and Podman are not preinstalled, but can be installed with `dnf` without repository license keys, or included in a custom runner image. Setup requires a GitHub organization and larger runner, then selecting a partner image and directing workflows to its runner label. Native testing can reveal library, SELinux, compiler, and container behavior differences before deployment. The excerpt recommends custom images to reduce repeated package installation time.

### Source excerpt

Modern software teams build code faster than ever. But building code faster creates a major roadblock when checking whether that code works. Both human code and AI-generated code cause problems if you lack a reliable test environment. When fast coding meets complex deployment setups, fixing broken pipelines by hand slows teams down. One problem you need to avoid is running automated tests on one Linux distribution when you deploy to another in production. The post Red Hat Enterprise Linux GitHub hosted runner images now generally available appeared first on Red Hat Developer.

## Build container images on your Runpod Pod with Runpod Weld

DevFeed: [Build container images on your Runpod Pod with Runpod Weld](<https://devfeed.tech/articles/build-container-images-on-your-runpod-pod-with-runpod-weld-124884.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/runpod-weld-build-images-on-your-pod>)

Author: Roman Przybyla

Published: 2026-11-09T23:41:48Z

Content type: tutorial

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [Docker Image](<https://devfeed.tech/topics/docker-image.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [demo](<https://devfeed.tech/tags/demo.md>), [docker](<https://devfeed.tech/tags/docker.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [inside](<https://devfeed.tech/tags/inside.md>), [pod](<https://devfeed.tech/tags/pod.md>)

### AI overview

Runpod Weld builds and pushes container images from a Runpod Pod without a Docker daemon; a separate container runtime is needed to run them. The guide shows checking the Pod with `rpweld doctor`, installing Weld on Linux amd64 (Debian 12 is the validated target), preparing a Dockerfile, and building and pushing an image to Docker Hub. Weld caches build stages, but builds are slower than local Docker, support only a subset of Dockerfile syntax, and are alpha software. Builds need Pod capabilities and filesystem permissions for `RUN` steps; Weld is not a security sandbox, and trusted Dockerfiles are recommended because `RUN` commands can access the Pod. Its image store and cache are separate from Docker's, finished builds are not automatically deleted, and registry tokens are base64-encoded rather than encrypted. The guide demonstrates deploying the pushed image on Runpod or running it on a Linux amd64 Docker host, and notes that private images require registry credentials.

### Source excerpt

Runpod Weld builds and pushes container images from inside a Runpod Pod, no Docker daemon needed. Build a demo image, push it, and run it on a Pod.

## Deep Dive Into Creating and Listing on the Runpod Hub

DevFeed: [Deep Dive Into Creating and Listing on the Runpod Hub](<https://devfeed.tech/articles/deep-dive-into-creating-and-listing-on-the-runpod-hub-121788.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/deep-dive-runpod-hub>)

Author: Brendan McKeag

Published: 2026-11-06T14:47:06Z

Content type: article

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [project release](<https://devfeed.tech/topics/project-release.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-deployment](<https://devfeed.tech/tags/ai-deployment.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [github](<https://devfeed.tech/tags/github.md>), [hub](<https://devfeed.tech/tags/hub.md>), [json](<https://devfeed.tech/tags/json.md>), [model](<https://devfeed.tech/tags/model.md>), [native](<https://devfeed.tech/tags/native.md>), [release](<https://devfeed.tech/tags/release.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [technical](<https://devfeed.tech/tags/technical.md>)

### AI overview

Runpod Hub uses GitHub releases to trigger builds and index serverless deployments: webhooks monitor a connected repository, and a release starts validation and infrastructure creation. A listing requires handler.py, a Dockerfile, hub.json and tests.json; the configuration files can live at the repository root or in .runpod, which takes precedence. The tests specification defines request cases, timeouts, GPU type and count, test environment variables, and supported CUDA versions. To submit, connect a repository, add the required files, create a release, and wait for Runpod staff review; approved listings can then be deployed, with initial endpoint settings derived from the JSON files. Listings are open source and GitHub connected, enabling users to inspect, fork, and modify implementations. The excerpt says creating a Hub listing is nearly identical to creating a serverless endpoint, but Hub offerings require staff vetting.

### Source excerpt

A deep technical dive into how the Runpod Hub streamlines serverless AI deployment with a GitHub-native, release-triggered model. Learn how hub.json and.

## Building Runpod templates: Your first custom template

DevFeed: [Building Runpod templates: Your first custom template](<https://devfeed.tech/articles/building-runpod-templates-your-first-custom-template-119778.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/building-runpod-templates-first-custom-template>)

Author: Roman Przybyla

Published: 2026-11-06T00:59:56Z

Content type: tutorial

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Snippet](<https://devfeed.tech/topics/snippet.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [custom](<https://devfeed.tech/tags/custom.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [docker-image](<https://devfeed.tech/tags/docker-image.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [guide](<https://devfeed.tech/tags/guide.md>), [pod](<https://devfeed.tech/tags/pod.md>), [pytorch](<https://devfeed.tech/tags/pytorch.md>), [template](<https://devfeed.tech/tags/template.md>), [templates](<https://devfeed.tech/tags/templates.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

The guide builds a reusable Runpod Pod setup by baking PyTorch and a GPU check script into a Docker image, publishing it to Docker Hub, and saving its settings in a private Runpod template. It pins the base image by digest, targets linux/amd64, and tests the script locally on CPU before checking normal container startup and running a GPU calculation in a Pod. Reusable software must be added to the Dockerfile and rebuilt; changes made in a running Pod are not captured by the template. A private template does not make a public image private, while private registries require pull credentials configured in Runpod. The guide also stresses matching the image to GPU and host CUDA support, reviewing deployment costs, and accounting for temporary container storage, persistent volume billing, and data loss when resources are terminated.

### Source excerpt

Step-by-step guide to building a custom PyTorch Docker image, pushing it to Docker Hub, and saving it as a reusable Runpod Pod template with a GPU test.

## SBOM Drift Detection: Catch Changes from Build to Production

DevFeed: [SBOM Drift Detection: Catch Changes from Build to Production](<https://devfeed.tech/articles/sbom-drift-detection-catch-changes-from-build-to-production-124331.md>)

Original publisher: [Read original article](<https://anchore.com/blog/sbom-drift-detection/>)

Author: teamanchore

Published: 2026-11-03T13:00:00Z

Content type: article

Language: en

Sources: [Anchore](<https://devfeed.tech/sources/anchore.md>)

Topics: [anchore](<https://devfeed.tech/topics/anchore.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [workload protection](<https://devfeed.tech/topics/workload-protection.md>)

Tags: [anchore-enterprise](<https://devfeed.tech/tags/anchore-enterprise.md>), [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [detection](<https://devfeed.tech/tags/detection.md>), [image](<https://devfeed.tech/tags/image.md>), [packages](<https://devfeed.tech/tags/packages.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [production](<https://devfeed.tech/tags/production.md>), [sbom](<https://devfeed.tech/tags/sbom.md>)

### AI overview

SBOM drift can leave vulnerability scans and compliance records based on components that no longer match what is running. The text describes two detection points: Anchore Enterprise's `tag_drift` gate compares successive builds of the same image tag, while the `anchore-k8s-inventory` agent polls Kubernetes to report running images for analysis through a `runtime_inventory` subscription. The gate applies only to image rule sets, not imported SBOMs, and needs a previous image with the same tag. The agent requires a runtime license entitlement. Suggested setup is to begin with `WARN`, optionally scope rules to OS packages, then consider `STOP` after observing drift volume; deploy the agent with read-only credentials. The excerpt presents these as complementary checks for build changes and runtime inventory.

### Source excerpt

The post SBOM Drift Detection: Catch Changes from Build to Production appeared first on Anchore.A nightly image rebuilds against node:20. Nothing in the Dockerfile changed. But a comparison of today's SBOM against yesterday's shows fourteen modified packages and two removed ones, none of which anyone touched on purpose. That's SBOM drift, and it happens on pipelines that are working exactly as designed. An introduction to SBOM drift SBOM drift [...]

## Building Guarded Entrypoint for Chainguard Containers

DevFeed: [Building Guarded Entrypoint for Chainguard Containers](<https://devfeed.tech/articles/building-guarded-entrypoint-for-chainguard-containers-113310.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/building-guarded-entrypoint-for-chainguard-containers>)

Published: 2026-11-02T00:00:00Z

Content type: release

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [chainguard custom assembly](<https://devfeed.tech/topics/chainguard-custom-assembly.md>), [chainguard images](<https://devfeed.tech/topics/chainguard-images.md>), [container-security](<https://devfeed.tech/topics/container-security.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [added](<https://devfeed.tech/tags/added.md>), [all](<https://devfeed.tech/tags/all.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [apps](<https://devfeed.tech/tags/apps.md>), [argument](<https://devfeed.tech/tags/argument.md>), [arguments](<https://devfeed.tech/tags/arguments.md>), [article](<https://devfeed.tech/tags/article.md>), [assembly](<https://devfeed.tech/tags/assembly.md>), [backend](<https://devfeed.tech/tags/backend.md>), [building](<https://devfeed.tech/tags/building.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [chainguard-containers](<https://devfeed.tech/tags/chainguard-containers.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [images](<https://devfeed.tech/tags/images.md>), [logic](<https://devfeed.tech/tags/logic.md>), [startup](<https://devfeed.tech/tags/startup.md>)

### AI overview

Guarded Entrypoint lets Chainguard Custom Assembly configure startup behavior without adding a derived image layer. An opt-in manifest places a built-in PID 1 init before the original entrypoint; it resolves environment-variable secret references from Google Secret Manager, Vault, or Consul, can build a Java truststore from mounted certificates, wait for a TCP endpoint or file, and control the command. It forwards signals, reaps orphaned processes, and returns the app's exit code. Unresolved secrets stop startup by default, with an optional open mode; an environment variable can bypass the init. Secrets are read only at startup, so leased credentials are not renewed. Only environment variables are resolved: Kubernetes expands `$(VAR)` in arguments before init runs, and expanded command secrets may be visible in `/proc/<pid>/cmdline`. With no secrets to resolve, median startup overhead is reported as under 4 ms on x86_64 and aarch64; backend calls add their network round-trip time.

### Source excerpt

Configure container startup logic without rebuilding images. See how Chainguard Guarded Entrypoint keeps your containers secure and verifiable.

## Track your Black October vulnerabilities from visibility to validated patch

DevFeed: [Track your Black October vulnerabilities from visibility to validated patch](<https://devfeed.tech/articles/track-your-black-october-vulnerabilities-from-visibility-to-validated-patch-105648.md>)

Original publisher: [Read original article](<https://newrelic.com/blog/security/black-october-cves-new-relic>)

Author: Krystle Portocarrero

Published: 2026-10-28T12:00:00Z

Content type: opinion

Language: en

Sources: [New Relic](<https://devfeed.tech/sources/new-relic.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [pip](<https://devfeed.tech/topics/pip.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [apm](<https://devfeed.tech/tags/apm.md>), [apps](<https://devfeed.tech/tags/apps.md>), [black](<https://devfeed.tech/tags/black.md>), [can](<https://devfeed.tech/tags/can.md>), [expert-observability](<https://devfeed.tech/tags/expert-observability.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [here](<https://devfeed.tech/tags/here.md>), [here-s](<https://devfeed.tech/tags/here-s.md>), [hit](<https://devfeed.tech/tags/hit.md>), [new-relic](<https://devfeed.tech/tags/new-relic.md>), [node2shell](<https://devfeed.tech/tags/node2shell.md>), [nodejs](<https://devfeed.tech/tags/nodejs.md>), [october](<https://devfeed.tech/tags/october.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [patch](<https://devfeed.tech/tags/patch.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [python](<https://devfeed.tech/tags/python.md>), [running](<https://devfeed.tech/tags/running.md>), [runtimes](<https://devfeed.tech/tags/runtimes.md>), [security-rx](<https://devfeed.tech/tags/security-rx.md>), [services](<https://devfeed.tech/tags/services.md>), [under](<https://devfeed.tech/tags/under.md>), [users](<https://devfeed.tech/tags/users.md>), [visibility](<https://devfeed.tech/tags/visibility.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

The excerpt explains that PHP2Shell and Node2Shell affect runtime components below application code, so image or code scans alone may not show which live services remain exposed. It describes New Relic Security RX using existing APM agents to report loaded libraries and runtime versions, and keeping a finding active until the affected version disappears from all reporting instances. The article's workflow is to filter recent vulnerabilities, inspect affected services and CVE remediation details, use logs and traces to assess context, and track affected versus no-longer-detected entities through rollout; agents report runtime data every 30 minutes by default, so status updates can lag. It recommends patching as the actual fix, watching service health during deployment, and treating PHP stopgaps only as a bridge. The excerpt also suggests pairing runtime visibility with scanners that identify potential exposure before deployment.

### Source excerpt

PHP2Shell and Node2Shell hit the runtimes under your apps. Here's how New Relic users can find exposed services and confirm the fix is running everywhere.

## Vercel Container Registry now supports 2 GB compressed image layers

DevFeed: [Vercel Container Registry now supports 2 GB compressed image layers](<https://devfeed.tech/articles/vercel-container-registry-now-supports-2-gb-compressed-image-layers-105509.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-container-registry-now-supports-2-gb-compressed-image-layers-new>)

Author: Andy Waller

Published: 2026-10-28T09:32:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [container images](<https://devfeed.tech/topics/container-images.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [commands](<https://devfeed.tech/tags/commands.md>), [container](<https://devfeed.tech/tags/container.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [docker](<https://devfeed.tech/tags/docker.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [layers](<https://devfeed.tech/tags/layers.md>), [link](<https://devfeed.tech/tags/link.md>), [login](<https://devfeed.tech/tags/login.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [toolchains](<https://devfeed.tech/tags/toolchains.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Container Registry now accepts compressed image layers up to 2 GB, up from 500 MB, so larger layers can be pushed without splitting them. The total image size limit remains 15 GB. This helps with images containing large toolchains or dependency sets, including custom Vercel Sandbox environments for coding-agent evaluations. To build and push, install Docker and the Vercel CLI, then run the supplied link, login, and build-and-push commands from the directory containing your Dockerfile.

### Source excerpt

Vercel Container Registry now supports up to 2 GB per compressed image layer, up from 500 MB, allowing larger layers to be pushed without splitting them. The total image size limit remains 15 GB. The higher layer limit is useful for images with large toolchains or dependency sets, such as custom Vercel Sandbox environments for coding-agent evaluations. With Docker and the Vercel CLI installed, run these commands from the directory containing your Dockerfile: Read the Vercel Container Registry getting-started guide to build, push, and pull your first container image. Read more

## One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images

DevFeed: [One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images](<https://devfeed.tech/articles/one-signed-answer-slsa-verification-summaries-for-registry-k8s-io-images-104466.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/28/registry-k8s-io-verification-summaries/>)

Author: The Kubernetes Authors

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [builder](<https://devfeed.tech/tags/builder.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [identity](<https://devfeed.tech/tags/identity.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [policy](<https://devfeed.tech/tags/policy.md>), [promotion](<https://devfeed.tech/tags/promotion.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [registry](<https://devfeed.tech/tags/registry.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

The Kubernetes image promoter now evaluates staging-image provenance against each project's policy in kubernetes/k8s.io, copies accepted attestations to registry.k8s.io, and publishes a signed SLSA verification summary (VSA) for each promoted image. Consumers can check the summary signer, verifier ID, result, and required build level with cosign and jq, or download it and run slsa-verifier with crane. Pin both signer and level: PASSED alone may mean only that promotion used a reviewed manifest, and an image without a policy can receive SLSA_BUILD_LEVEL_UNEVALUATED. SPO's v1.1.1 operator images, binaries, and Helm chart reach level 3; its bundle reaches only level 1 in that release, so a level 3 check fails. Projects need signed staging provenance, a manifest policy, and a test run. Cloud Build can provide level 1; level 3 requires provenance from an isolated GitHub workflow, then verification and attachment to the matching staging digest. Roll out policies in warn mode, test with kpromo cip, verify summaries, then use require to block violations. Summaries are created once at promotion, and most images promoted before October 2026 lack them; multi-architecture platform images need,

### Source excerpt

The Kubernetes community has been signing its container images since v1.24, and the images that kpromo, the Kubernetes image promoter (rewritten earlier this year), copies to registry.k8s.io get a signature. A signature answers one question: did this image go through the official promotion process? It does not answer the more interesting one: how was this image built, and from which source? Projects can attach signed SLSA provenance to their images to answer that. But to check it yourself, you have to know who builds each image, which identity signs its provenance, which builder it claims and which repository it comes from, for every project you pull from. That is a lot to ask, and in practice few people do it. Since October 2026, the image promoter does this work for you, once, at promotion time, and publishes the answer as a signed SLSA verification summary (VSA) for every image it promotes. In this blog post, I'd like to explain how it works, how you can verify it, and how your project can get its images verified at SLSA build level 1 or 3. How does it work? A project declares a provenance policy in its promoter manifest in kubernetes/k8s.io: who may sign its build attestations, which builders it trusts and at which level, and which source repositories its images come from. When a reviewed pull request promotes an image, the promoter evaluates the attestations of the staging image against that policy with the SLSA verifier, copies the accepted attestations to registry.k8s.io and writes the summary: flowchart LR build["Project build"] staging[("Staging registry")] policy["Provenance policy
in kubernetes/k8s.io"] promoter["Image promoter"] prod[("registry.k8s.io")] users["Users and clusters"] build -- "image and
signed provenance" --> staging staging --> promoter policy --> promoter promoter -- "image, attestations,
verification summary" --> prod prod -- "verify one summary" --> users The summaries are signed by a dedicated identity, promoter-summaries@

## Deploy a container from a plain Dockerfile

DevFeed: [Deploy a container from a plain Dockerfile](<https://devfeed.tech/articles/deploy-a-container-from-a-plain-dockerfile-102770.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/deploy-a-container-from-a-plain-dockerfile>)

Author: Jeff See

Published: 2026-10-27T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [beta](<https://devfeed.tech/tags/beta.md>), [build](<https://devfeed.tech/tags/build.md>), [container](<https://devfeed.tech/tags/container.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [django](<https://devfeed.tech/tags/django.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [file](<https://devfeed.tech/tags/file.md>), [framework](<https://devfeed.tech/tags/framework.md>), [functions](<https://devfeed.tech/tags/functions.md>), [image](<https://devfeed.tech/tags/image.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [project](<https://devfeed.tech/tags/project.md>), [root](<https://devfeed.tech/tags/root.md>), [run](<https://devfeed.tech/tags/run.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [service](<https://devfeed.tech/tags/service.md>), [services](<https://devfeed.tech/tags/services.md>), [set](<https://devfeed.tech/tags/set.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

When no other framework is detected, Vercel can build a root Dockerfile or Containerfile with its Container preset and route traffic to the resulting image. If detection finds another framework, such as Django, that framework takes precedence; select the Container framework with `vercel project update --framework container` or `"framework": "container"` in `vercel.json`. A `Dockerfile.vercel` or `Containerfile.vercel` still takes precedence over framework detection. Multi-service projects configure `services` and a per-service `entrypoint` in `vercel.json`. The Container runtime is in beta, runs on Vercel Functions, and uses Active CPU pricing.

### Source excerpt

You can now deploy a plain root Dockerfile or Containerfile on Vercel's Container runtime when no other framework is detected. Vercel selects the Container preset, builds that file, and routes all traffic to the resulting image. To get started with containers on Vercel, add a Dockerfile: When project detection matches another framework, such as Django, that framework still wins. To build use the Dockerfile or Containerfile instead, run vercel project update --framework container, or set the framework in vercel.json: A Dockerfile.vercel or Containerfile.vercel continues to win over a detected framework, and multi-service projects still use vercel.json services with a per-service entrypoint. The Container runtime is in beta, runs on Vercel Functions, and is billed with Active CPU pricing. Read the Container runtime documentation to get started. Read more

## eMudhra CA compromise: eight private keys, and one of them is 4

DevFeed: [eMudhra CA compromise: eight private keys, and one of them is 4](<https://devfeed.tech/articles/emudhra-ca-compromise-eight-private-keys-and-one-of-them-is-4-95730.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/emudhra-ca-compromise>)

Author: Jorian Woltjer

Published: 2026-10-22T11:53:00Z

Content type: article

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [enterprise certificate authority certificates](<https://devfeed.tech/topics/enterprise-certificate-authority-certificates.md>), [Security Attacks](<https://devfeed.tech/topics/security-attacks.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>)

Tags: [alpine](<https://devfeed.tech/tags/alpine.md>), [apple](<https://devfeed.tech/tags/apple.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [ca](<https://devfeed.tech/tags/ca.md>), [certificate-transparency](<https://devfeed.tech/tags/certificate-transparency.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [ci](<https://devfeed.tech/tags/ci.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [containers](<https://devfeed.tech/tags/containers.md>), [curl](<https://devfeed.tech/tags/curl.md>), [emudhra](<https://devfeed.tech/tags/emudhra.md>), [emudhra-ca-compromise](<https://devfeed.tech/tags/emudhra-ca-compromise.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [keys](<https://devfeed.tech/tags/keys.md>), [private](<https://devfeed.tech/tags/private.md>), [private-keys](<https://devfeed.tech/tags/private-keys.md>), [threats](<https://devfeed.tech/tags/threats.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

The article reports that eight eMudhra intermediate CA private keys were recoverable from their public certificates, each requiring at most 256 guesses; one key was 4. Browser and platform vendors blocked the certificates through revocation updates, but many command-line clients, servers, containers, runtimes and IoT devices may still trust them because they do not check revocation or carry stale CA bundles. The article says forged certificates require an attacker to be on the network path, and clients enforcing certificate transparency could not have been targeted; it does not establish whether attackers used the keys. Recommended steps are to update OS and browser software, install the distribution- and runtime-specific CA updates, rebuild images and restart services, and test affected clients for SSL failure. Bundled trust stores and built-in macOS command-line tools may need separate fixes. Aikido says its image checks flag affected bundled and system certificate stores separately.

### Source excerpt

Eight eMudhra CA keys could be guessed in at most 256 tries, and one is just the number 4. Who is affected, why curl lagged browsers, and how to fix it. Category: Vulnerabilities & Threats

## How to Diagnose vite: not found After npm ci in a Container Build

DevFeed: [How to Diagnose vite: not found After npm ci in a Container Build](<https://devfeed.tech/articles/how-to-diagnose-vite-not-found-after-npm-ci-in-a-container-build-93154.md>)

Original publisher: [Read original article](<https://www.freecodecamp.org/news/diagnose-vite-not-found-npm-ci-container-build/>)

Author: Ahmed Tariq

Published: 2026-10-21T16:03:14Z

Content type: tutorial

Language: en

Sources: [Free Code Camp](<https://devfeed.tech/sources/freecodecamp-programming-tutorials-python-javascript-git-more.md>)

Topics: [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Vite](<https://devfeed.tech/topics/vite.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [azure](<https://devfeed.tech/tags/azure.md>), [build](<https://devfeed.tech/tags/build.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [build-tools](<https://devfeed.tech/tags/build-tools.md>), [cache](<https://devfeed.tech/tags/cache.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [development-environment](<https://devfeed.tech/tags/development-environment.md>), [docker](<https://devfeed.tech/tags/docker.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [vite](<https://devfeed.tech/tags/vite.md>)

### AI overview

The `vite: not found` error followed a failed `npm ci`: 528 lockfile entries pointed to an internal package proxy unreachable from the Azure Container Registry build, leaving `node_modules` empty. The tutorial traces the failure by checking the dependency directory, inventorying `resolved` URL hosts, and inspecting earlier npm errors; `Exit handler never called!` alone does not identify the cause. For confirmed public packages, it rewrites only the approved URL prefix while preserving versions and integrity values, then guards each independent install with `npm ci --include=dev` and an executable check for Vite. It recommends verifying the rewrite count, remaining hosts, dependency identity, build, and output. Private packages need a reachable authenticated registry; substituting their URLs may be unsafe.

### Source excerpt

I recently worked on a project where a Node.js application used Vite to compile its frontend. It worked in a browser-hosted development environment, but its image build failed after the move to Azure

## The distroless security gap: Why bottom-up containers are the next evolution in OCI images

DevFeed: [The distroless security gap: Why bottom-up containers are the next evolution in OCI images](<https://devfeed.tech/articles/the-distroless-security-gap-why-bottom-up-containers-are-the-next-evolution-in-oci-images-89991.md>)

Original publisher: [Read original article](<https://thenewstack.io/distroless-container-security-gap/>)

Author: Lily Rivers-Klee

Published: 2026-10-19T13:00:00Z

Content type: article

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [container-security](<https://devfeed.tech/topics/container-security.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [distroless](<https://devfeed.tech/topics/distroless.md>), [Buildpacks](<https://devfeed.tech/topics/buildpacks.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [cloud-native-ecosystem](<https://devfeed.tech/tags/cloud-native-ecosystem.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [containers](<https://devfeed.tech/tags/containers.md>), [dockerfiles](<https://devfeed.tech/tags/dockerfiles.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [security](<https://devfeed.tech/tags/security.md>), [sponsor-cncf](<https://devfeed.tech/tags/sponsor-cncf.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>)

### AI overview

The article describes bottom-up container builds as a way to combine minimal images with preserved package metadata for vulnerability scanning. It outlines package slicing, declarative builds, and using Pebble as PID 1 to manage child processes.

### Source excerpt

Ever tried to shrink your container images to reduce their attack surface? If you have, you've likely discovered a frustrating The post The distroless security gap: Why bottom-up containers are the next evolution in OCI images appeared first on The New Stack.

## JetBrains .NET Day Online 2026: Watch the Recordings

DevFeed: [JetBrains .NET Day Online 2026: Watch the Recordings](<https://devfeed.tech/articles/jetbrains-net-day-online-2026-watch-the-recordings-89905.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/dotnet/2026/10/19/jetbrains-dotnet-day-online-2026-watch-the-recordings/>)

Author: Mehul Harry

Published: 2026-10-19T08:00:00Z

Content type: news

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>)

Topics: [deveco](<https://devfeed.tech/topics/deveco.md>), [.NET](<https://devfeed.tech/topics/net.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [asyncapi supply chain attack](<https://devfeed.tech/topics/asyncapi-supply-chain-attack.md>), [native aot](<https://devfeed.tech/topics/native-aot.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [api](<https://devfeed.tech/tags/api.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [build](<https://devfeed.tech/tags/build.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [container](<https://devfeed.tech/tags/container.md>), [container-apps](<https://devfeed.tech/tags/container-apps.md>), [containers](<https://devfeed.tech/tags/containers.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [data-api-builder](<https://devfeed.tech/tags/data-api-builder.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [events](<https://devfeed.tech/tags/events.md>), [jetbrains](<https://devfeed.tech/tags/jetbrains.md>), [net](<https://devfeed.tech/tags/net.md>), [net-days-online](<https://devfeed.tech/tags/net-days-online.md>), [resharper](<https://devfeed.tech/tags/resharper.md>), [rider](<https://devfeed.tech/tags/rider.md>)

### AI overview

JetBrains .NET Day Online 2026 recordings are available on YouTube. The event recap highlights sessions on AI-assisted development with JetBrains tools, distributed .NET patterns, C# performance, AI development workflows, software supply-chain security, modular monoliths, .NET interoperability, SQL MCP Server, and scaling Blazor workloads with .NET Aspire and Azure Container Apps.

### Source excerpt

Every session from October 7 is now on YouTube. .NET Day Online 2026 took place on October 7. Thanks to everyone who watched the livestream and asked questions in the chat! If you missed a session, or want to watch one again, all of them are now online. Watch the full playlist Here's a quick [...]

## Atomic AlmaLinux moves to the latest bootc tooling

DevFeed: [Atomic AlmaLinux moves to the latest bootc tooling](<https://devfeed.tech/articles/atomic-almalinux-moves-to-the-latest-bootc-tooling-86164.md>)

Original publisher: [Read original article](<https://almalinux.org/blog/2026-10-13-atomic-bootc-modernization/>)

Author: Alex Iribarren Atomic SIG Lead; Director; AlmaLinux OS Foundation

Published: 2026-10-13T00:00:00Z

Content type: release

Language: en

Sources: [AlmaLinux](<https://devfeed.tech/sources/blog-on-almalinux.md>)

Topics: [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [NixOS](<https://devfeed.tech/topics/nixos.md>)

Tags: [almalinux](<https://devfeed.tech/tags/almalinux.md>), [arm64](<https://devfeed.tech/tags/arm64.md>), [build](<https://devfeed.tech/tags/build.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [release](<https://devfeed.tech/tags/release.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

AlmaLinux's Atomic SIG released atomic-ci v13, updating the workflows used to build, sign, and publish bootc images and ISOs. The release adopts bootc-base-imagectl for image rechunking and image-builder for ISOs, adds live-session and aarch64 ISO support, and introduces other workflow changes. Maintainers of existing respins need to update for breaking changes in v13.

### Source excerpt

The Atomic SIG has just released v13 of atomic-ci, and it's the biggest change to our build tooling in quite some time. When we started the Atomic SIG last year, we built our images with the best tools available at the time. Since then, the bootc community has learned a lot from those tools and built better ones. This release moves us onto them, aligning with the rest of the bootc community. Most of that is plumbing you'll never see, but some of it you will, like ISOs that boot into a live session, and ISOs for aarch64.

## Creating a Vlad Diffusion Template for Runpod

DevFeed: [Creating a Vlad Diffusion Template for Runpod](<https://devfeed.tech/articles/creating-a-vlad-diffusion-template-for-runpod-84662.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/vlad-diffusion-template-runpod>)

Author: Brandon Ikeler

Published: 2026-10-10T23:21:42Z

Content type: tutorial

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [stable-diffusion](<https://devfeed.tech/topics/stable-diffusion.md>), [automatic1111](<https://devfeed.tech/topics/automatic1111.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [cli](<https://devfeed.tech/tags/cli.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-containers](<https://devfeed.tech/tags/docker-containers.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [docker-images](<https://devfeed.tech/tags/docker-images.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [how-to](<https://devfeed.tech/tags/how-to.md>)

### AI overview

The tutorial explains how to build and launch a custom Vlad Diffusion template on Runpod. It covers adapting Dockerfiles, building and pushing container images, configuring the template, and accessing JupyterLab. The author also describes reducing the image size from about 43 GB to roughly 20 GB through layer caching and multi-stage builds.

### Source excerpt

Want a custom spin on Stable Diffusion? This post shows you how to create and launch your own Vlad Diffusion template inside Runpod.

## Don't give AI agents root. Make them propose the next system state.

DevFeed: [Don't give AI agents root. Make them propose the next system state.](<https://devfeed.tech/articles/don-t-give-ai-agents-root-make-them-propose-the-next-system-state-77468.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/10/08/dont-give-ai-agents-root-make-them-propose-the-next-system-state/>)

Author: Mauro Morales | CNCF Ambassador

Published: 2026-10-08T22:21:41Z

Content type: opinion

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [OpenShell](<https://devfeed.tech/topics/openshell.md>)

Tags: [agent-harnesses](<https://devfeed.tech/tags/agent-harnesses.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [blog](<https://devfeed.tech/tags/blog.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [containers](<https://devfeed.tech/tags/containers.md>)

### AI overview

The article argues that AI agents should not receive unrestricted root access to production systems. Instead, agents can inspect and propose changes to a versioned system state, with proposals passing through review, testing, image building, signing, and release. Immutable host images and workload isolation can help enforce this separation, though neither provides complete protection on its own.

### Source excerpt

The uncomfortable question In the past few months, I've been hearing different versions of the same question: under what conditions can we safely allow an autonomous system to operate a machine? It comes up when my...

## Avoid Errors by Selecting the Proper Resources for Your Pod

DevFeed: [Avoid Errors by Selecting the Proper Resources for Your Pod](<https://devfeed.tech/articles/avoid-errors-by-selecting-the-proper-resources-for-your-pod-78076.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/avoid-pod-errors-runpod-resources>)

Author: Brendan McKeag

Published: 2026-10-08T20:47:14Z

Content type: tutorial

Language: en

Sources: [Runpod Blog.](<https://devfeed.tech/sources/runpod-blog.md>)

Topics: [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [NUMA](<https://devfeed.tech/topics/numa.md>), [Operating system](<https://devfeed.tech/topics/operating-system.md>), [GPU instancing](<https://devfeed.tech/topics/gpu-instancing.md>)

Tags: [all](<https://devfeed.tech/tags/all.md>), [container](<https://devfeed.tech/tags/container.md>), [cuda](<https://devfeed.tech/tags/cuda.md>), [errors](<https://devfeed.tech/tags/errors.md>), [ram](<https://devfeed.tech/tags/ram.md>), [vram](<https://devfeed.tech/tags/vram.md>)

### AI overview

The article explains how to diagnose and address Runpod pod errors caused by insufficient container storage or RAM/VRAM. It covers checking container utilization, increasing volume size, choosing a different GPU configuration, and reducing model memory requirements through quantization.

### Source excerpt

Common errors when spinning up pods often stem from insufficient container space or RAM/VRAM. This post explains how to identify and fix both issues by.

## Container Apps Express Reaches GA on a Newly Generally Available Sandbox Layer

DevFeed: [Container Apps Express Reaches GA on a Newly Generally Available Sandbox Layer](<https://devfeed.tech/articles/container-apps-express-reaches-ga-on-a-newly-generally-available-sandbox-layer-63130.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/container-apps-express-sandboxes/>)

Author: Steef-Jan Wiggers

Published: 2026-10-01T06:31:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-container-apps](<https://devfeed.tech/tags/azure-container-apps.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [container-apps-express-sandboxes](<https://devfeed.tech/tags/container-apps-express-sandboxes.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [microsoft-azure](<https://devfeed.tech/tags/microsoft-azure.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [news](<https://devfeed.tech/tags/news.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

Microsoft made Azure Container Apps Express generally available alongside Container Apps Sandboxes, its hardware-isolated microVM layer. Express takes a container image and handles compute, ingress, and scaling, including scaling to zero; Sandboxes support suspend and resume with snapshots. The article outlines Express's feature limits, migration path, and intended uses for agent platforms and secure code execution.

### Source excerpt

Microsoft has made Azure Container Apps Express generally available alongside Container Apps Sandboxes, the microVM compute layer it runs on. Express skips environment provisioning and scales to zero, with subsecond startup from prewarmed pools. Custom domains, zone redundancy, Key Vault references, OpenTelemetry and Dapr are not supported. By Steef-Jan Wiggers

## Docker Explained: A Practical Guide to Containers for Developers

DevFeed: [Docker Explained: A Practical Guide to Containers for Developers](<https://devfeed.tech/articles/docker-explained-a-practical-guide-to-containers-for-developers-87899.md>)

Original publisher: [Read original article](<https://jsdev.space/docker-fundamentals-guide/>)

Author: Anton Liberant

Published: 2026-07-02T00:00:00Z

Content type: tutorial

Language: en

Sources: [JavaScript Development](<https://devfeed.tech/sources/javascript-development.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [container-security](<https://devfeed.tech/topics/container-security.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [containers](<https://devfeed.tech/tags/containers.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-compose](<https://devfeed.tech/tags/docker-compose.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [guide](<https://devfeed.tech/tags/guide.md>)

### AI overview

This practical guide explains Docker's purpose and core concepts, including images, containers, layers, Dockerfiles, build caching, storage, and networking. It shows how Docker supports reproducible environments and offers guidance on containerizing applications, optimizing builds, and applying security and deployment practices.

### Source excerpt

Learn Docker from the ground up. Understand containers, images, isolation, Dockerfiles, best practices, and real-world workflows with practical examples.

## Running the OpenTelemetry Collector as a Lambda

DevFeed: [Running the OpenTelemetry Collector as a Lambda](<https://devfeed.tech/articles/running-the-opentelemetry-collector-as-a-lambda-77926.md>)

Original publisher: [Read original article](<https://www.honeycomb.io/blog/running-opentelemetry-collector-lambda>)

Author: Jessica Kerr (Jessitron)

Published: 2026-06-08T20:30:00Z

Content type: tutorial

Language: en

Sources: [Honeycomb Blog](<https://devfeed.tech/sources/honeycomb-blog.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [function as a service](<https://devfeed.tech/topics/function-as-a-service.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>)

### AI overview

The tutorial explains how to run the OpenTelemetry Collector on AWS Lambda for intermittent telemetry using a container image, Lambda Web Adapter, and a Function URL. It covers bearer authentication, deployment permissions, verification, and troubleshooting. The configuration uses synchronous export without batching or sending queues because Lambda freezes containers between invocations. The approach suits stateless processing at low volume and lacks durable buffering during backend outages.

### Source excerpt

The OpenTelemetry Collector is usually deployed as a long-running process, but when telemetry is rare, it makes sense to run it as a Lambda function instead. Here's how to do it.

## The Best Container Registries in 2026

DevFeed: [The Best Container Registries in 2026](<https://devfeed.tech/articles/the-best-container-registries-in-2026-95501.md>)

Original publisher: [Read original article](<https://blog.railway.com/p/best-container-registries-2026>)

Author: Angelo Saraceno

Published: 2026-05-26T00:00:00Z

Content type: article

Language: en

Sources: [Railway](<https://devfeed.tech/sources/railway.md>)

Topics: [container-security](<https://devfeed.tech/topics/container-security.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [image retention policy](<https://devfeed.tech/topics/image-retention-policy.md>), [GitHub Container Registry](<https://devfeed.tech/topics/github-container-registry.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [pull through cache](<https://devfeed.tech/topics/pull-through-cache.md>), [trivy](<https://devfeed.tech/topics/trivy.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [best](<https://devfeed.tech/tags/best.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [container](<https://devfeed.tech/tags/container.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [railway](<https://devfeed.tech/tags/railway.md>), [ranking](<https://devfeed.tech/tags/ranking.md>), [registries](<https://devfeed.tech/tags/registries.md>), [registry](<https://devfeed.tech/tags/registry.md>)

### AI overview

The article argues that registry choice affects deploy latency, image security and compliance, access control, retention costs, and the operational burden of keeping deploy pipelines working. It compares ten platforms by fit and trade-offs: Railway keeps images within its deploy platform but cannot serve as a general-purpose registry; Docker Hub suits public images but imposes pull limits; GitHub and GitLab registries align with their CI and auth systems, with scanning or storage limitations; ECR, Artifact Registry, and ACR fit workloads in their respective clouds, with costs and scanning features that vary; Quay emphasizes scanning, while Cloudflare targets edge pulls but has a younger tooling ecosystem; Harbor supports self-hosting and air-gapped use but requires ongoing operations. The decision criteria are compute location, scanning needs, auth, image visibility, retention, and outage responsibility.

### Source excerpt

Container registries are the under-thought-about piece of cloud infrastructure. The six jobs a real registry has to do, and an honest ranking of the platforms in 2026.

## Introducing: Modal 1.0

DevFeed: [Introducing: Modal 1.0](<https://devfeed.tech/articles/introducing-modal-1-0-79870.md>)

Original publisher: [Read original article](<https://modal.com/blog/introducing-client-1-0>)

Author: Modal

Published: 2025-06-09T12:00:00Z

Content type: release

Language: en

Sources: [Modal](<https://devfeed.tech/sources/modal.md>)

Topics: [SDK](<https://devfeed.tech/topics/sdk.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cloud-compute](<https://devfeed.tech/tags/cloud-compute.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [config](<https://devfeed.tech/tags/config.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [maturity](<https://devfeed.tech/tags/maturity.md>), [v1](<https://devfeed.tech/tags/v1.md>)

### AI overview

Modal released version 1.0 of its Python client SDK, emphasizing greater stability, a more predictable API, and fewer expected breaking changes. The release makes local package inclusion explicit, separates concurrency configuration into its own decorator, consolidates container file management in the Image class, and introduces batched client updates. Modal also describes plans to explore SDKs for other languages and workflows designed for AI tools.

### Source excerpt

We've released v1.0 of the Modal client, marking a new milestone of maturity and stability for our platform.

[Next page](<https://devfeed.tech/topics/container-image-building.md?cursor=WyIyMDI1LTA2LTA5VDEyOjAwOjAwKzAwOjAwIiwgImY0Y2IzODdjLWE2MWQtNGQyOC1hNzE3LWFiOTk4ZmM4N2FlYyJd>)