# Dockerfile

A Dockerfile is a text document containing instructions Docker uses to build an image.

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

## 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.

## 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

## Your Docker Host Is Patched. Your Containers Might Not Be.

DevFeed: [Your Docker Host Is Patched. Your Containers Might Not Be.](<https://devfeed.tech/articles/your-docker-host-is-patched-your-containers-might-not-be-100735.md>)

Original publisher: [Read original article](<https://www.virtualizationhowto.com/2026/10/your-docker-host-is-patched-your-containers-might-not-be/>)

Author: Brandon Lee

Published: 2026-10-26T12:22:13Z

Content type: article

Language: en

Sources: [Virtualization Howto](<https://devfeed.tech/sources/virtualization-howto.md>)

Topics: [container-security](<https://devfeed.tech/topics/container-security.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [image tags vs digests](<https://devfeed.tech/topics/image-tags-vs-digests.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Ubuntu](<https://devfeed.tech/topics/ubuntu.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [about-you](<https://devfeed.tech/tags/about-you.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [containers](<https://devfeed.tech/tags/containers.md>), [discussion](<https://devfeed.tech/tags/discussion.md>), [docker](<https://devfeed.tech/tags/docker.md>), [first](<https://devfeed.tech/tags/first.md>), [howto](<https://devfeed.tech/tags/howto.md>), [i](<https://devfeed.tech/tags/i.md>), [patched](<https://devfeed.tech/tags/patched.md>), [patching](<https://devfeed.tech/tags/patching.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [post](<https://devfeed.tech/tags/post.md>), [reddit](<https://devfeed.tech/tags/reddit.md>), [this](<https://devfeed.tech/tags/this.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>), [vs](<https://devfeed.tech/tags/vs.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Patching a Docker host does not patch software inside its containers: containers share the host kernel but carry their own filesystems, applications, and dependencies. The article recommends inventorying containers with `docker ps` or `docker compose images`, then checking relevant documentation and advisories and scanning images with Trivy or Grype (also available through Dockhand). A newer image is not automatically safer, so review release notes and interpret scan results. Updating requires pulling and recreating containers with Compose; restarting alone keeps the old image. Tags may be mutable or fixed, while digest pins require changing the referenced digest to select new content. For images you build, rebuild from an updated base, account for pinned references and build cache, then verify the running image and application. A changed image ID confirms replacement, not that a specific vulnerability was fixed. Host, engine, and image updates need separate checks.

### Source excerpt

This past week, I saw some discussion on Reddit around the recent PHP2shell vulnerability and how some were wondering on patching their hosts vs patching their Docker containers. This confusion... The post Your Docker Host Is Patched. Your Containers Might Not Be. appeared first on Virtualization Howto.

## GitHub Actions Runner v2.338.1 release

DevFeed: [GitHub Actions Runner v2.338.1 release](<https://devfeed.tech/articles/v2-338-1-95811.md>)

Original publisher: [Read original article](<https://github.com/actions/runner/releases/tag/v2.338.1>)

Author: github-actions\[bot\]

Published: 2026-10-22T14:15:24Z

Content type: release

Language: en

Sources: [GitHub Action Runners](<https://devfeed.tech/sources/github-action-runners.md>)

Topics: [self-hosted runner](<https://devfeed.tech/topics/self-hosted-runner.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actions](<https://devfeed.tech/tags/actions.md>), [buildx](<https://devfeed.tech/tags/buildx.md>), [codeql](<https://devfeed.tech/tags/codeql.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [docker](<https://devfeed.tech/tags/docker.md>), [dotnet](<https://devfeed.tech/tags/dotnet.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [eslint](<https://devfeed.tech/tags/eslint.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [js](<https://devfeed.tech/tags/js.md>), [lint](<https://devfeed.tech/tags/lint.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [repository](<https://devfeed.tech/tags/repository.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [security](<https://devfeed.tech/tags/security.md>), [update](<https://devfeed.tech/tags/update.md>), [v2](<https://devfeed.tech/tags/v2.md>)

### AI overview

Actions Runner 2.338.1 updates dependencies and build tooling, moves internal runner operations to Node 24, and adds broker-listener WebSocket connectivity probes. Other listed changes include support for `$/` self-repository references in action manifests, retaining the owned session ID when deleting broker sessions, and updating the Node.js 20 removal date to September 23, 2026. The excerpt provides download and extraction instructions for Windows x64/arm64, macOS x64/arm64, and Linux x64/arm64/arm; Windows guidance recommends installing under the drive root to reduce service identity permission and long-path issues. Progressive release means availability may vary by enterprise, organization, or repository.

### Source excerpt

What's Changed Bump @typescript-eslint/eslint-plugin from 8.67.0 to 8.68.0 in /src/Misc/expressionFunc/hashFiles by @dependabot[bot] in #4661 chore: update Node versions by @github-actions[bot] in #4665 Bump browserslist from 4.28.5 to 4.28.9 in /src/Misc/expressionFunc/hashFiles by @dependabot[bot] in #4677 Update Docker to v29.8.0 and Buildx to v0.37.0 by @github-actions[bot] in #4676 Update Node.js 20 removal date to September 23rd, 2026 by @salmanmkc in #4685 Bump @typescript-eslint/parser from 8.68.0 to 8.69.0 in /src/Misc/expressionFunc/hashFiles by @dependabot[bot] in #4673 Bump Microsoft.DevTunnels.Connections from 1.3.51 to 1.3.56 by @dependabot[bot] in #4667 Bump github/codeql-action from 4.37.8 to 4.37.9 by @dependabot[bot] in #4664 Bump lint-staged from 17.3.0 to 17.5.0 in /src/Misc/expressionFunc/hashFiles by @dependabot[bot] in #4663 Bump System.Formats.Asn1 and System.Security.Cryptography.Pkcs by @dependabot[bot] in #4688 Bump @typescript-eslint/parser from 8.69.0 to 8.70.0 in /src/Misc/expressionFunc/hashFiles by @dependabot[bot] in #4705 Bump js-yaml from 4.3.1 to 4.3.2 in /src/Misc/expressionFunc/hashFiles by @dependabot[bot] in #4696 Bump lint-staged from 17.5.0 to 17.5.1 in /src/Misc/expressionFunc/hashFiles by @dependabot[bot] in #4715 chore: update Node versions by @github-actions[bot] in #4716 Bump github/codeql-action from 4.37.9 to 4.38.0 by @dependabot[bot] in #4713 Bump @typescript-eslint/eslint-plugin from 8.68.0 to 8.70.0 in /src/Misc/expressionFunc/hashFiles by @dependabot[bot] in #4714 Update Buildx to v0.37.1 by @github-actions[bot] in #4712 Bump System.Text.Encoding.CodePages from 10.0.11 to 10.0.12 by @dependabot[bot] in #4701 Update dotnet sdk to latest version @8.0.425 by @github-actions[bot] in #4717 Bump github/codeql-action from 4.38.0 to 4.38.1 by @dependabot[bot] in #4731 Update Docker to v29.8.1 by @github-actions[bot] in #4730 Accept $/ self-repository references in action manifests by @nodeselector in #4669 Bump Microsoft

## Don't Hand Claude Your Docker Socket -- Build It a Guarded One

DevFeed: [Don't Hand Claude Your Docker Socket -- Build It a Guarded One](<https://devfeed.tech/articles/don-t-hand-claude-your-docker-socket-build-it-a-guarded-one-93924.md>)

Original publisher: [Read original article](<https://hackernoon.com/dont-hand-claude-your-docker-socket-build-it-a-guarded-one?source=rss>)

Author: Siva Sai Krishna Suryadevara

Published: 2026-10-21T21:17:14Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [anthropic](<https://devfeed.tech/topics/anthropic.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [ci](<https://devfeed.tech/tags/ci.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-ai](<https://devfeed.tech/tags/claude-ai.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [compose](<https://devfeed.tech/tags/compose.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [llm-security](<https://devfeed.tech/tags/llm-security.md>), [llm-tools](<https://devfeed.tech/tags/llm-tools.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [python](<https://devfeed.tech/tags/python.md>), [socket](<https://devfeed.tech/tags/socket.md>)

### AI overview

The Python FastMCP server gives Claude four Docker tools: container listing, inspection, log retrieval with anomaly scanning, and guarded restart. A read-only socket mount does not block Docker API writes, so restart is disabled by default and, when enabled, checked against Docker's resolved container name to prevent ID-based bypasses; a denylist takes precedence over an optional allowlist. Inspection returns environment variable names but withholds values, while log output and scans are capped. The server returns structured errors for daemon failures and keeps diagnostics off stdio JSON-RPC stdout. Its 47 tests mock Docker and do not require a daemon. The article cautions that tool-layer guards are not a security boundary for other processes with socket access, and suggests a filtering proxy for API-level restriction. It also pins the official `mcp` SDK below 2 because the documented FastMCP API changed in 2.x.

### Source excerpt

A Python MCP server that gives Claude read-only access to Docker, with a name-resolved restart guard, secret redaction, and a 47-test mocked suite.

## 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

## Why Docker Rebuilds Every Layer in CI, Even With -- cache-to

DevFeed: [Why Docker Rebuilds Every Layer in CI, Even With -- cache-to](<https://devfeed.tech/articles/why-docker-rebuilds-every-layer-in-ci-even-with-cache-to-85892.md>)

Original publisher: [Read original article](<https://blog.devops.dev/why-docker-rebuilds-every-layer-in-ci-even-with-cache-to-25e8eb4783c8?source=rss----33f8b2d9a328---4>)

Author: Daniel Valev

Published: 2026-10-13T10:52:12Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [ci](<https://devfeed.tech/tags/ci.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [layer](<https://devfeed.tech/tags/layer.md>), [programming](<https://devfeed.tech/tags/programming.md>), [rebuilds](<https://devfeed.tech/tags/rebuilds.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

A fresh GitHub Actions runner has no remembered BuildKit state, so a Dockerfile that rebuilds quickly on a laptop may rebuild every layer on each CI commit. The excerpt says the common recommendation is to add `--cache-to` and `--cache-from`, which works for a simple single-stage Dockerfile; it does not provide enough of the article to explain the listed cache pitfalls or how to address them.

### Source excerpt

mode=min, orphaned cache mounts, per-commit build args, and shared cache scopes: the defaults that throw your BuildKit cache away on... Continue reading on DevOps.dev "

## Optimizing Django Docker Images With Multi-Stage Builds and Slim Python Runtimes

DevFeed: [Optimizing Django Docker Images With Multi-Stage Builds and Slim Python Runtimes](<https://devfeed.tech/articles/optimizing-django-docker-images-with-multi-stage-builds-and-slim-python-runtimes-85092.md>)

Original publisher: [Read original article](<https://hackernoon.com/optimizing-django-docker-images-with-multi-stage-builds-and-slim-python-runtimes?source=rss>)

Author: Himashi Meththasena

Published: 2026-10-11T17:22:05Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Django](<https://devfeed.tech/topics/django.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [container-security](<https://devfeed.tech/topics/container-security.md>), [Python](<https://devfeed.tech/topics/python.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [django](<https://devfeed.tech/tags/django.md>), [django-deployment](<https://devfeed.tech/tags/django-deployment.md>), [django-docker](<https://devfeed.tech/tags/django-docker.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-buildkit](<https://devfeed.tech/tags/docker-buildkit.md>), [docker-containerization](<https://devfeed.tech/tags/docker-containerization.md>), [docker-image](<https://devfeed.tech/tags/docker-image.md>), [docker-image-optimization](<https://devfeed.tech/tags/docker-image-optimization.md>), [docker-images](<https://devfeed.tech/tags/docker-images.md>), [docker-multi-stage-builds](<https://devfeed.tech/tags/docker-multi-stage-builds.md>), [docker-security](<https://devfeed.tech/tags/docker-security.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [python](<https://devfeed.tech/tags/python.md>), [python-dockerfile](<https://devfeed.tech/tags/python-dockerfile.md>)

### AI overview

This tutorial shows how to create a smaller, more secure Django container image by separating dependency compilation from runtime with Docker multi-stage builds. It recommends a slim Python base image, copying installed packages into the runtime stage, and running the application as a non-root user. It also describes enabling BuildKit in CI/CD and reports that the example can reduce an image from 1.2 GB to under 250 MB.

### Source excerpt

Learn how to build smaller, more secure Django Docker images using multi-stage builds, slim Python images, and non-root execution.

## Docker Best Practices for Building and Running Production Containers

DevFeed: [Docker Best Practices for Building and Running Production Containers](<https://devfeed.tech/articles/docker-best-practices-for-building-and-running-production-containers-59446.md>)

Original publisher: [Read original article](<https://kodekloud.com/blog/docker-best-practices-for-building-and-running-production-containers/>)

Author: Pramodh Kumar M

Published: 2026-09-24T18:00:39Z

Content type: tutorial

Language: en

Sources: [KodeKloud](<https://devfeed.tech/sources/kubernetes-kodekloud-blog-devops-cloud-kubernetes-ai-tutorials-more.md>)

Topics: [container](<https://devfeed.tech/topics/container.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [container-healthcheck](<https://devfeed.tech/tags/container-healthcheck.md>), [container-signal-handling](<https://devfeed.tech/tags/container-signal-handling.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distroless-images](<https://devfeed.tech/tags/distroless-images.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-best-practices-production-containers](<https://devfeed.tech/tags/docker-best-practices-production-containers.md>), [docker-layer-caching](<https://devfeed.tech/tags/docker-layer-caching.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [dockerfile-best-practices](<https://devfeed.tech/tags/dockerfile-best-practices.md>), [dockerignore](<https://devfeed.tech/tags/dockerignore.md>), [image-size-reduction](<https://devfeed.tech/tags/image-size-reduction.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [multi-stage-build](<https://devfeed.tech/tags/multi-stage-build.md>), [non-root-container-user](<https://devfeed.tech/tags/non-root-container-user.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [read-only-filesystem-container](<https://devfeed.tech/tags/read-only-filesystem-container.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

A practical guide to building and running production containers. It covers image size, Dockerfile layer ordering, multi-stage builds, non-root execution, signal handling, environment-based configuration, secrets, debugging, and runtime behavior.

### Source excerpt

Most production container problems are decided in about fifteen lines of Dockerfile. Here is what to put in them, why each line is there, and what breaks when it is missing.

## From Dockerfile to Kit: the Docker Sandboxes Kit Specification

DevFeed: [From Dockerfile to Kit: the Docker Sandboxes Kit Specification](<https://devfeed.tech/articles/from-dockerfile-to-kit-the-docker-sandboxes-kit-specification-59553.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-sandbox-kit-spec/>)

Author: Jin Kim

Published: 2026-09-24T16:00:00Z

Content type: article

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [docker-sandboxes](<https://devfeed.tech/tags/docker-sandboxes.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [network](<https://devfeed.tech/tags/network.md>), [oci](<https://devfeed.tech/tags/oci.md>), [open-container-initiative-oci](<https://devfeed.tech/tags/open-container-initiative-oci.md>), [products](<https://devfeed.tech/tags/products.md>), [sandbox-kit](<https://devfeed.tech/tags/sandbox-kit.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [security](<https://devfeed.tech/tags/security.md>), [v3](<https://devfeed.tech/tags/v3.md>), [volumes](<https://devfeed.tech/tags/volumes.md>)

### AI overview

Docker's Sandbox Kit Specification v3 defines an open-source OCI image format for packaging an AI agent's runtime configuration, including tools, MCP servers, credentials, network rules, volumes, skills, and instructions. The article contrasts agent sandboxes with containers and explains why Docker Sandboxes use microVM isolation.

### Source excerpt

Docker's Sandbox Kit Specification v3 packages an AI agent's network rules, credentials, and volumes as an ordinary, pinnable OCI image.

## Updating \`apk add\` and \`apt install\` definitions in Dockerfiles with Renovate

DevFeed: [Updating \`apk add\` and \`apt install\` definitions in Dockerfiles with Renovate](<https://devfeed.tech/articles/updating-apk-add-and-apt-install-definitions-in-dockerfiles-with-renovate-53102.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/09/18/renovate-regex-dockerfile-apk/>)

Author: Jamie Tanna

Published: 2026-09-18T17:30:05Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [APK](<https://devfeed.tech/topics/apk.md>), [apt](<https://devfeed.tech/topics/apt.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [apk](<https://devfeed.tech/tags/apk.md>), [apt](<https://devfeed.tech/tags/apt.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [chainguard-images](<https://devfeed.tech/tags/chainguard-images.md>), [dockerfiles](<https://devfeed.tech/tags/dockerfiles.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>)

### AI overview

This article explains how Renovate now natively updates pinned packages installed with apk add, apt install, and apt-get install in Dockerfiles. It discusses reproducible builds, support for Wolfi and Chainguard Images, and the temporary need to configure registry URLs explicitly.

### Source excerpt

If you're writing Dockerfiles that install packages using system package managers, such as apk or apt, you might be pinning your versions of packages, to make sure that you have more reproducible builds, or if you're on a rolling release distribution like Wolfi and Chainguard Images, you want to make sure you only get package versions you want. When these system package manager versions are pinned, it can then be a little cumbersome to keep them updated in an automated fashion, as most tools don't have a way to automagically parse your files and propose updates. So you're probably one one of two camps - "I'll get my AI agent to go and update it for me" or "we'll not update anything until things break". I've previously had this managed - at least for apk add updates - by using a Custom Regex Manager with Renovate to keep them updated, which required you break the install command over multiple lines: # ... RUN apk upgrade --no-cache && \ apk add --no-cache \ bash=5.2.37-r2 \ py3-pip \ python3 \ rsyslog=8.2412.0-r1 \ runit=2.2.0 ENV APP_HOST=0.0.0.0 ENV app_port=5000 ENV SNAPP_PORT 5000 This isn't that much of a problem - as it also improves readability - but you generally want the tools to work around you, not vice versa. As of earlier this morning, we've shipped inbuilt support in Renovate, so if you have a Dockerfile with apk add, or an apt install (or apt-get install) like below, you'll be able to receive package updates for them 🎉 For instance, with the following Dockerfile: # SPDX-License-Identifier: AGPL-3.0-only # Via https://docs.renovatebot.com/modules/manager/dockerfile/#run-apt-install-support FROM debian:trixie RUN apt-get update \ && apt-get install -y --no-install-recommends \ # newlines for readability only curl=8.14.1-2 \ git=1:2.47.3-0+deb13u1 \ && rm -rf /var/lib/apt/lists/* Renovate will detect that you have a package pin for curl and git, and if there are updates available, will propose them. Right now, we don't currently auto-detect the distributi

## How buildpacks help enterprises finally operate container security controls at scale

DevFeed: [How buildpacks help enterprises finally operate container security controls at scale](<https://devfeed.tech/articles/how-buildpacks-help-enterprises-finally-operate-container-security-controls-at-scale-55165.md>)

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

Author: Catherine Edelveis

Published: 2026-09-18T14:00:00Z

Content type: article

Language: en

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

Topics: [Buildpacks](<https://devfeed.tech/topics/buildpacks.md>), [container-security](<https://devfeed.tech/topics/container-security.md>), [container](<https://devfeed.tech/topics/container.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [vulnerability management](<https://devfeed.tech/topics/vulnerability-management.md>), [software bill of materials](<https://devfeed.tech/topics/software-bill-of-materials.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [buildpacks](<https://devfeed.tech/tags/buildpacks.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [containers](<https://devfeed.tech/tags/containers.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [scale](<https://devfeed.tech/tags/scale.md>), [scanners](<https://devfeed.tech/tags/scanners.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>), [standards](<https://devfeed.tech/tags/standards.md>)

### AI overview

The article explains how buildpacks can standardize application image builds and help platform teams centrally govern container security controls, including runtime images, SBOM generation, metadata, and update workflows. It also describes why patches and vulnerability fixes may fail to reach production consistently across enterprise workloads.

### Source excerpt

Container security controls often fail less because organizations lack standards, scanners, or best practices, and more. After all, every service The post How buildpacks help enterprises finally operate container security controls at scale appeared first on The New Stack.

## Simplify application migrations to AWS with Elastic Beanstalk

DevFeed: [Simplify application migrations to AWS with Elastic Beanstalk](<https://devfeed.tech/articles/simplify-application-migrations-to-aws-with-elastic-beanstalk-50013.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/simplify-application-migrations-to-aws-with-elastic-beanstalk/>)

Author: Nitish Kulkarni

Published: 2026-09-17T19:29:03Z

Content type: release

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Network](<https://devfeed.tech/topics/network.md>), [container](<https://devfeed.tech/topics/container.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-elastic-beanstalk](<https://devfeed.tech/tags/aws-elastic-beanstalk.md>), [compute](<https://devfeed.tech/tags/compute.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [learning-levels](<https://devfeed.tech/tags/learning-levels.md>), [migration](<https://devfeed.tech/tags/migration.md>), [networking](<https://devfeed.tech/tags/networking.md>), [observability](<https://devfeed.tech/tags/observability.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

AWS Elastic Beanstalk introduces a deployment mode for managing multiple applications on shared infrastructure operated and upgraded by AWS. The post describes migrations from other platforms and legacy applications, including Windows .NET, Java, and PHP applications, with support for source code, Dockerfiles, and prebuilt container images.

### Source excerpt

Today, AWS Elastic Beanstalk introduces a new deployment mode that manages multiple applications on shared infrastructure that AWS creates, operates, and upgrades for you. Whether you provide source code, a Dockerfile, or a prebuilt container image, Elastic Beanstalk takes care of building and deploying your application. It also configures networking, autoscaling, and observability. You manage [...]

## Automate Docker Registry Creation with Harness and Terraform

DevFeed: [Automate Docker Registry Creation with Harness and Terraform](<https://devfeed.tech/articles/automate-docker-registry-creation-with-harness-and-terraform-31421.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/how-to-automate-docker-registry-creation-with-harness-pipelines-and-terraform>)

Author: Shibam Dhar

Published: 2026-09-16T00:00:00Z

Content type: tutorial

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [Infrastructure as code](<https://devfeed.tech/topics/infrastructure-as-code.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [docker-registry](<https://devfeed.tech/tags/docker-registry.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [registry](<https://devfeed.tech/tags/registry.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

A tutorial shows how to use Harness Pipelines and the Harness Terraform Provider to provision a uniquely named Docker Registry, build and push a container image, and deploy it to Kubernetes. It covers Terraform execution in a CI step, passing output variables between stages, and rolling updates with automatic rollback.

### Source excerpt

Provision a fresh Docker Registry with Terraform, build your container image into it, and deploy to Kubernetes in one | Blog

## How Developers Prevent Production Risk at the Source

DevFeed: [How Developers Prevent Production Risk at the Source](<https://devfeed.tech/articles/how-developers-prevent-production-risk-at-the-source-53937.md>)

Original publisher: [Read original article](<https://www.wiz.io/blog/prevent-production-risk-at-code-stage>)

Author: Mike McGuire

Published: 2026-09-03T00:31:46Z

Content type: article

Language: en

Sources: [Wiz](<https://devfeed.tech/sources/wiz-blog-rss-feed.md>)

Topics: [Risk](<https://devfeed.tech/topics/risk.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Security](<https://devfeed.tech/topics/security.md>), [Code](<https://devfeed.tech/topics/code.md>), [Software](<https://devfeed.tech/topics/software.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>), [AI Models](<https://devfeed.tech/topics/ai-models.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [code](<https://devfeed.tech/tags/code.md>), [container](<https://devfeed.tech/tags/container.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developers](<https://devfeed.tech/tags/developers.md>), [frontier-ai-models](<https://devfeed.tech/tags/frontier-ai-models.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [risk](<https://devfeed.tech/tags/risk.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [software](<https://devfeed.tech/tags/software.md>), [wiz-code](<https://devfeed.tech/tags/wiz-code.md>)

### AI overview

This article explains why fixing security vulnerabilities during coding is cheaper and safer than patching them after deployment. It uses a vulnerable Docker base image to contrast a localized source change with production-wide remediation, and discusses how AI agents are accelerating vulnerability discovery and exploit development.

### Source excerpt

Fixing security vulnerabilities in code takes seconds, while patching in production creates high operational costs and risk. Discover how empowering developers as your first line of defense eliminates exposure across every phase of your software pipeline.

## Securing Docker images

DevFeed: [Securing Docker images](<https://devfeed.tech/articles/securing-docker-images-51649.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/securing-docker-images>)

Author: Nicholas Thomson

Published: 2026-08-28T20:29:00Z

Content type: tutorial

Language: en

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

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [Docker Image](<https://devfeed.tech/topics/docker-image.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [vulnerability management](<https://devfeed.tech/topics/vulnerability-management.md>), [Debian](<https://devfeed.tech/topics/debian.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cve](<https://devfeed.tech/tags/cve.md>), [debian](<https://devfeed.tech/tags/debian.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-images](<https://devfeed.tech/tags/docker-images.md>), [guides](<https://devfeed.tech/tags/guides.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [patch](<https://devfeed.tech/tags/patch.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

A guide to securing Docker images by removing unused packages, managing vulnerabilities in required dependencies, and keeping base images patched. It explains image layers, inherited attack surface, hardened images, and patch delivery without necessarily changing pinned base-image versions.

### Source excerpt

Most of a container's vulnerabilities come from the base image. How to harden Docker images, why hardening is ongoing, and how to patch the base you already run. Category: Guides & Best Practices

## Azure Developer CLI (azd) - August 2026

DevFeed: [Azure Developer CLI (azd) - August 2026](<https://devfeed.tech/articles/azure-developer-cli-azd-august-2026-50023.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/azure-sdk/azure-developer-cli-azd-august-2026/>)

Author: Kristen Womack, Jeffrey C.

Published: 2026-08-27T17:39:02Z

Content type: release

Language: en

Sources: [Azure SDK Blog](<https://devfeed.tech/sources/azure-sdk-blog.md>)

Topics: [azd](<https://devfeed.tech/topics/azd.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Extension](<https://devfeed.tech/topics/extension.md>), [azure functions](<https://devfeed.tech/topics/azure-functions.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [ACR](<https://devfeed.tech/topics/acr.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [acr](<https://devfeed.tech/tags/acr.md>), [azd](<https://devfeed.tech/tags/azd.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-developer-cli](<https://devfeed.tech/tags/azure-developer-cli.md>), [azure-functions](<https://devfeed.tech/tags/azure-functions.md>), [azure-sdk](<https://devfeed.tech/tags/azure-sdk.md>), [cli](<https://devfeed.tech/tags/cli.md>), [codespaces](<https://devfeed.tech/tags/codespaces.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer](<https://devfeed.tech/tags/developer.md>), [discussion](<https://devfeed.tech/tags/discussion.md>), [docker](<https://devfeed.tech/tags/docker.md>), [extension](<https://devfeed.tech/tags/extension.md>), [github](<https://devfeed.tech/tags/github.md>), [go](<https://devfeed.tech/tags/go.md>), [java](<https://devfeed.tech/tags/java.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [net](<https://devfeed.tech/tags/net.md>), [python](<https://devfeed.tech/tags/python.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [services](<https://devfeed.tech/tags/services.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [vscode](<https://devfeed.tech/tags/vscode.md>)

### AI overview

The August 2026 Azure Developer CLI release blog covers versions 1.30.0 through 1.32.0. It announces general availability for the extension framework, new container-based Azure Functions deployment options, direct extension-bundle installation from HTTPS URLs, layered provisioning dependency inference, and breaking terminology changes.

### Source excerpt

Welcome to the August 2026 edition of the Azure Developer CLI (azd) release blog. This post covers releases 1.30.0, 1.31.0, 1.31.1, 1.31.2, and 1.32.0. To share your feedback and questions, join the August release discussion on GitHub. Highlights: The azd extension framework is generally available. Azure Functions services can deploy from a Dockerfile, a prebuilt [...] The post Azure Developer CLI (azd) - August 2026 appeared first on Azure SDK Blog.

## Howto Push a Docker Image to a Private Registry

DevFeed: [Howto Push a Docker Image to a Private Registry](<https://devfeed.tech/articles/howto-push-a-docker-image-to-a-private-registry-87923.md>)

Original publisher: [Read original article](<https://jsdev.space/howto/push-docker-image/>)

Author: anton liberant

Published: 2026-08-21T00: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>), [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-compose](<https://devfeed.tech/tags/docker-compose.md>), [docker-login](<https://devfeed.tech/tags/docker-login.md>), [dockerfile](<https://devfeed.tech/tags/dockerfile.md>), [howto](<https://devfeed.tech/tags/howto.md>), [private-registry](<https://devfeed.tech/tags/private-registry.md>)

### AI overview

This tutorial shows how to build a Docker image, authenticate with a private registry, tag and push the image, then pull and run it on a server. It recommends using explicit version tags and `--password-stdin` to handle credentials, and describes automating the workflow with CI/CD.

### Source excerpt

Learn how to build a Docker image, authenticate with a private registry, push the image, and pull it onto another server.

## We rebuilt the Linux microVM stack on Apple Silicon

DevFeed: [We rebuilt the Linux microVM stack on Apple Silicon](<https://devfeed.tech/articles/we-rebuilt-the-linux-microvm-stack-on-apple-silicon-17799.md>)

Original publisher: [Read original article](<https://encore.dev/blog/firecracker-apple-silicon>)

Author: Ivan Cernja

Published: 2026-08-18T00:00:00Z

Content type: article

Language: en

Sources: [Encore Updates](<https://devfeed.tech/sources/encore-updates.md>)

Topics: [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>)

Tags: [docker](<https://devfeed.tech/tags/docker.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [go](<https://devfeed.tech/tags/go.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>)

### AI overview

Encore rebuilt its Linux microVM development stack to work on Apple Silicon. The article describes crackling, an API that uses Firecracker on Linux and Apple's hypervisor on macOS, along with the tooling needed to run the same build system on developer laptops and in production.

### Source excerpt

Maybe we should have just moved everyone to Linux.

## What Is a Container Registry and How to Use One

DevFeed: [What Is a Container Registry and How to Use One](<https://devfeed.tech/articles/what-is-a-container-registry-and-how-to-use-one-17491.md>)

Original publisher: [Read original article](<https://kodekloud.com/blog/what-is-a-container-registry-and-how-to-use-one/>)

Author: Pramodh Kumar M

Published: 2026-08-10T17:48:35Z

Content type: tutorial

Language: en

Sources: [KodeKloud](<https://devfeed.tech/sources/kubernetes-kodekloud-blog-devops-cloud-kubernetes-ai-tutorials-more.md>)

Topics: [container images](<https://devfeed.tech/topics/container-images.md>), [content addressed store](<https://devfeed.tech/topics/content-addressed-store.md>), [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>)

Tags: [base-images](<https://devfeed.tech/tags/base-images.md>), [cache](<https://devfeed.tech/tags/cache.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [containers](<https://devfeed.tech/tags/containers.md>), [content-addressed-store](<https://devfeed.tech/tags/content-addressed-store.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [docker-login](<https://devfeed.tech/tags/docker-login.md>), [docker-pull-rate-limits](<https://devfeed.tech/tags/docker-pull-rate-limits.md>), [docker-registry](<https://devfeed.tech/tags/docker-registry.md>), [harbor](<https://devfeed.tech/tags/harbor.md>), [image-manifest](<https://devfeed.tech/tags/image-manifest.md>), [image-retention-policy](<https://devfeed.tech/tags/image-retention-policy.md>), [image-scanning](<https://devfeed.tech/tags/image-scanning.md>), [image-tags-vs-digests](<https://devfeed.tech/tags/image-tags-vs-digests.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [private-registry](<https://devfeed.tech/tags/private-registry.md>), [pull-through-cache](<https://devfeed.tech/tags/pull-through-cache.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

This guide explains how container registries store and distribute container images, emphasizing the distinction between mutable tags and immutable content digests. It also covers pushing, pulling, authentication, Docker Hub rate limits, caching, scanning, and retention.

### Source excerpt

A tag is a bookmark somebody else can move. A digest is the image itself. Once that distinction lands, reproducible builds, supply chain security, and every it worked yesterday mystery make sense.

## Run any Dockerfile on Vercel

DevFeed: [Run any Dockerfile on Vercel](<https://devfeed.tech/articles/run-any-dockerfile-on-vercel-732.md>)

Original publisher: [Read original article](<https://vercel.com/blog/dockerfile-on-vercel>)

Author: Kevin Sundstrom

Published: 2026-06-30T16:00:00Z

Content type: article

Language: en

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

Topics: [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Web app](<https://devfeed.tech/topics/webapp.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [http](<https://devfeed.tech/tags/http.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [network](<https://devfeed.tech/tags/network.md>), [observability](<https://devfeed.tech/tags/observability.md>), [traces](<https://devfeed.tech/tags/traces.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel introduces support for deploying applications from a Dockerfile.vercel file. The platform builds, stores, deploys, and autoscales container images on Fluid compute, with pricing based on active CPU usage. The article demonstrates a Go HTTP server and explains that other HTTP-speaking applications, including Rails, Spring Boot, Express, Laravel, ASP.NET, FastAPI, Java, PHP, and nginx-backed servers, can use the same deployment model.

### Source excerpt

You have a server in a container. Maybe it's a Go service, a Rails app, a Spring Boot API, or a web server behind nginx. It speaks HTTP. It listens on a port. It just needs somewhere to run. Add a Dockerfile.vercel file to your project, and Vercel builds, stores, deploys, and autoscales the image on Fluid compute, so you pay only for the CPU your code uses. No daemon to run locally, registry to set up, or cluster to babysit. How it works Here is a small HTTP server in Go, listening on $PORT: Add a Dockerfile.vercel file that builds it into a small image and runs it: Then deploy: That is it. Two files, and you are live. Every git push rebuilds the image and hands you a fresh preview URL. Or run vercel to deploy without committing. We used Go in this example, but any language works. Rails, Spring Boot, Express, Laravel, ASP.NET, FastAPI, and a web server behind nginx all deploy the same way. The only rule is that your server listens on $PORT, which defaults to 80. If it speaks HTTP, it deploys. Yes, even Java. And yes, even PHP. What you get A container on Vercel is a first-class citizen. It runs on the same platform, and the same compute, as your frontend and the rest of your services on Vercel. A preview deployment for every push: Every commit gets its own immutable URL you can open, share, and roll back to. Autoscaling, in both directions: Traffic arrives and you scale out. Traffic stops and your instances wind down. You never size a fleet or guess a concurrency number. Active CPU pricing: Fluid compute bills for the time your code is actually running, so an idle server, parked on a slow query or an upstream API, isn't burning CPU while it waits. You pay for execution time, not wall time. Observability, included: Logs, traces, and metrics for your container live in the same dashboard as everything else you ship. One project, one domain: Your container sits beside your frontend and your other services and talks to them privately over the Vercel network. Your full st

## Bring your Dockerfile to Vercel Functions

DevFeed: [Bring your Dockerfile to Vercel Functions](<https://devfeed.tech/articles/bring-your-dockerfile-to-vercel-functions-820.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/bring-your-dockerfile-to-vercel-functions>)

Author: Joe Haddad

Published: 2026-06-30T00: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](<https://devfeed.tech/topics/container.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [containers](<https://devfeed.tech/tags/containers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-containers](<https://devfeed.tech/tags/docker-containers.md>), [oci](<https://devfeed.tech/tags/oci.md>), [routing](<https://devfeed.tech/tags/routing.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Functions now support deploying HTTP servers from Dockerfile or Containerfile projects using OCI-compatible container images on Fluid compute. Images are built, pushed to Vercel Container Registry, and deployed on each commit, while retaining Vercel preview deployments, logs, routing, and autoscaling benefits.

### Source excerpt

Vercel Functions now support deploying HTTP servers from a Dockerfile or Containerfile, using Open Container Initiative (OCI) compatible images on Fluid compute. This makes it easier to bring existing applications written in any language to Vercel while keeping the preview deployments, logs, routing, and autoscaling benefits of using Vercel Functions and Fluid compute. To use container images with your functions, create a project with a Dockerfile.vercel (or Containerfile.vercel) file that starts an HTTP server listening on $PORT: This image will be built, pushed, and deployed on every commit to Vercel Container Registry. Learn more about using container images in the docs and see seven ways you can use Docker containers on Vercel. Read more

## Introducing VCR: Vercel Container Registry

DevFeed: [Introducing VCR: Vercel Container Registry](<https://devfeed.tech/articles/introducing-vcr-vercel-container-registry-989.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/introducing-vcr-vercel-container-registry>)

Author: Wilson Wang

Published: 2026-06-30T00: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](<https://devfeed.tech/topics/container.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [docker](<https://devfeed.tech/tags/docker.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [oci](<https://devfeed.tech/tags/oci.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [operations](<https://devfeed.tech/tags/operations.md>), [registry](<https://devfeed.tech/tags/registry.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Vercel introduces Vercel Container Registry, an OCI-compliant registry for pushing, pulling, and managing container images through standard Docker workflows. It supports project-scoped authorization, OIDC or access-token authentication, automatic optimization for Sandboxes and Functions, and integration with Vercel build and deployment workflows.

### Source excerpt

You can now push, pull, and manage container images directly on Vercel. Vercel Container Registry is an OCI-compliant image registry hosted on Vercel infrastructure. It works with standard workflows like docker push, docker pull, and docker tag, so there's nothing new to learn or tooling to migrate. A Vercel project can have unlimited repositories. You can create and manage them through the Vercel dashboard, or push directly to VCR, which creates the repository for you on the fly. Operations use the same authorization controls as the rest of Vercel. You can authenticate with OIDC or an access token, provided the token has access to the project scope. Optimized for Fluid Compute When you push an image, VCR automatically optimizes it in the background for use in Sandboxes and Functions. VCR stores a precompiled snapshot and serves that snapshot when the image is requested. These snapshots use the same format as Sandbox Snapshots, which are optimized to run on Fluid Compute. Build and deploy on Vercel The Vercel build environment is automatically set up with authentication for the current project, so you can build and store images as part of the build and deploy process. You can also bring your Dockerfile to Vercel directly and host it with Vercel Functions or Vercel Sandboxes. Read more about VCR in the documentation. Read more

## AWS debuts Lambda MicroVMs with up to 8 hours runtime

DevFeed: [AWS debuts Lambda MicroVMs with up to 8 hours runtime](<https://devfeed.tech/articles/aws-debuts-lambda-microvms-with-up-to-8-hours-runtime-47911.md>)

Original publisher: [Read original article](<https://www.devclass.com/devops/2026/06/24/aws-debuts-lambda-microvms-with-up-to-8-hours-runtime/5260139>)

Author: Tim Anderson

Published: 2026-06-24T12:04:00Z

Content type: news

Language: en

Sources: [DevClass.com](<https://devfeed.tech/sources/devclass-com.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [container](<https://devfeed.tech/topics/container.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [prompt injection](<https://devfeed.tech/topics/prompt-injection.md>), [Bug Bounty](<https://devfeed.tech/topics/bugbounty.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [compute](<https://devfeed.tech/tags/compute.md>), [containers](<https://devfeed.tech/tags/containers.md>), [core](<https://devfeed.tech/tags/core.md>), [devops](<https://devfeed.tech/tags/devops.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [graviton](<https://devfeed.tech/tags/graviton.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [linux](<https://devfeed.tech/tags/linux.md>), [making](<https://devfeed.tech/tags/making.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [prompt-injection](<https://devfeed.tech/tags/prompt-injection.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [virtual](<https://devfeed.tech/tags/virtual.md>), [virtual-machine](<https://devfeed.tech/tags/virtual-machine.md>)

### AI overview

AWS introduced Lambda MicroVMs, built on Firecracker, to run isolated Linux containers for up to eight hours. The feature supports workloads such as code isolation, vulnerability scanning, CI/CD, and AI-agent execution, with suspend-and-resume behavior and consumption-based pricing.

### Source excerpt

AWS has introduced Lambda MicroVMs, built on its Firecracker virtual machine monitor, which can run ...

[Next page](<https://devfeed.tech/topics/dockerfile.md?cursor=WyIyMDI2LTA2LTI0VDEyOjA0OjAwKzAwOjAwIiwgIjJmMTY1ZThiLTRmYTktNDYyMy05OTZiLWUyZmI3ZDYyYzgzOCJd>)