# dockerfiles Published articles for dockerfiles. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Introducing Chainguard OS Packages: Secure ingredients for custom container builds DevFeed: [Introducing Chainguard OS Packages: Secure ingredients for custom container builds]() Original publisher: [Read original article]() Published: 2026-03-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard os](), [container images](), [Docker Hardened Images](), [Vulnerabilities](), [Linux](), [Automation](), [Dockerfile](), [Open Source](), [bazel](), [chainguard sboms](), [APK]() Tags: [apk](), [apko](), [automation](), [base-images](), [bazel](), [chainguard](), [chainguard-containers](), [chainguard-libraries](), [chainguard-os](), [chainguard-os-packages](), [chainguard-packages](), [chainguard-sboms](), [container](), [container-images](), [cve](), [dockerfiles](), [open-source](), [sboms](), [secure-software-packages](), [software-packages](), [vulnerabilities](), [zero-cve-packages]() ### AI overview Chainguard introduces Chainguard OS Packages, a service providing continuously maintained, enterprise-grade packages and base images for teams that build custom container images. Customers retain control over image composition and build tooling while Chainguard handles package sourcing, rebuilding, vulnerability remediation, and SBOM generation. ### Source excerpt Chainguard OS Packages are enterprise-grade, zero-CVE packages and base images built and continuously maintained in the Chainguard Factory. ## Guardener automates migration from legacy Dockerfiles to secure Chainguard container images DevFeed: [Guardener automates migration from legacy Dockerfiles to secure Chainguard container images]() Original publisher: [Read original article]() Published: 2026-03-17T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [AI Development](), [Dockerfile](), [migration](), [Security](), [Automation](), [supply-chain-security]() Tags: [agent](), [ai](), [ai-agents](), [ai-migration-agents](), [audit](), [automation](), [chainguard-ai-tools](), [chainguard-guardener](), [chainguard-the-guardener](), [container-images](), [distroless](), [dockerfiles](), [migration](), [security](), [vulnerabilities]() ### AI overview Chainguard introduces Guardener, an AI-native agent that helps engineering teams migrate legacy Dockerfiles to minimal Chainguard container images. It gathers environmental context, rebuilds Dockerfiles layer by layer, tests the results, and provides post-migration insights on image size, CVEs, and filesystem changes. ### Source excerpt Guardener is an AI-native agent that accelerates engineering teams' adoption of trusted open source artifacts across software development and deployment. ## Native .NET Buildpack Support is Now Available on App Platform DevFeed: [Native .NET Buildpack Support is Now Available on App Platform]() Original publisher: [Read original article]() Author: Bikram Gupta Published: 2026-03-05T21:21:25Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [.NET](), [Deployment](), [SDK](), [Dockerfile](), [Git](), [ASP.NET](), [NuGet]() Tags: [asp-net-core](), [c-sharp](), [deployment](), [digitalocean](), [dockerfiles](), [dotnet](), [f-sharp](), [git](), [net](), [product-updates](), [release](), [sdk]() ### AI overview DigitalOcean App Platform now supports native .NET buildpacks, allowing developers to deploy .NET applications from Git repositories without maintaining Dockerfiles. The platform detects the project, selects the SDK version, restores dependencies, and builds the application for production. ### Source excerpt The .NET ecosystem continues to power a significant share of enterprise and cloud-native applications, from web APIs and microservices to full-stack applications built with ASP.NET Core. Developers building with C#, F#, and Visual Basic need a deployment experience that matches the productivity of the framework itself: push code, and let the platform handle the rest. Today, we're excited to announce native .NET buildpack support on DigitalOcean App Platform. You can now deploy your .NET applications directly from a Git repository without writing or maintaining Dockerfiles. App Platform automatically detects your .NET project, installs the correct SDK version, and builds your application for production. Benefits Zero Configuration: Push your .NET code to a Git repository, and App Platform handles runtime detection, SDK installation, and build configuration automatically--no Dockerfile required. Multi-Language Support: Build applications in C#, Visual Basic, or F# using the .NET and ASP.NET Core frameworks, all with the same streamlined deployment experience. Automatic SDK Management: App Platform selects the appropriate .NET SDK version based on your project's TargetFramework or global.json configuration, supporting .NET 8.0, 9.0, and 10.0. Production-Ready Defaults: The buildpack compiles with the Release configuration by default and automatically detects ASP.NET Core web applications to configure the correct process type. How Detection Works Once you connect your Git repository, App Platform identifies your application as a .NET project by looking for specific files in your repository root. App Platform confirms a .NET application if it detects any of the following: Solution files: *.sln, *.slnx Project files: *.csproj, *.vbproj, *.fsproj File-based apps: *.cs Once detected, the buildpack takes over: SDK Detection: Determines the required .NET SDK version from your TargetFramework property or global.json file Dependency Restore: Runs dotnet restore to fetch NuGet pa ## Be my base image: Introducing Linky's Matchmaker DevFeed: [Be my base image: Introducing Linky's Matchmaker]() Original publisher: [Read original article]() Published: 2026-02-12T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Dockerfile](), [chainguard containers](), [Containers](), [Vulnerabilities](), [App](), [Web]() Tags: [base-images](), [chainguard](), [chainguard-containers](), [chainguard-images](), [chainguard-valentine-s-day](), [comparisons](), [container-images](), [containers](), [dockerfile-converter](), [dockerfiles](), [documentation](), [images](), [secure-by-default](), [vulnerabilities]() ### AI overview Linky's Matchmaker is a web-based app that analyzes Dockerfiles, recommends compatible Chainguard Containers, and generates downloadable converted Dockerfiles. It also provides image availability checks, documentation and tag links, and vulnerability comparisons. ### Source excerpt Linky's Matchmaker converts your Dockerfile to Chainguard Containers, recommending secure, minimal base images and generating an updated file in minutes ## New Chainguard Academy Course: Getting Started with Chainguard's Dockerfile Converter DevFeed: [New Chainguard Academy Course: Getting Started with Chainguard's Dockerfile Converter]() Original publisher: [Read original article]() Published: 2025-07-25T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [dockerfile converter](), [Dockerfile](), [Containers](), [chainguard containers](), [Command-line interface](), [MCP Server]() Tags: [chainguard](), [chainguard-academy](), [chainguard-containers](), [chainguard-images](), [command-line](), [containers](), [course](), [dockerfile-converter](), [dockerfiles](), [getting-started](), [how-to](), [mcp](), [secure-container-images](), [zero-cve-containers]() ### AI overview Chainguard Academy has launched a hands-on course that teaches developers and DevOps teams how to use Chainguard's Dockerfile Converter to convert existing Dockerfiles into secure, minimal Chainguard container images. The course covers installation, Dockerfile instruction handling, customization, advanced usage, and best practices. ### Source excerpt Discover how to use Chainguard's new Dockerfile Converter tool to close the gap between legacy Dockerfiles and secure containers in our new course. ## Announcing Dockerfile Converter: Fast and Easy Migration to Use Chainguard Containers DevFeed: [Announcing Dockerfile Converter: Fast and Easy Migration to Use Chainguard Containers]() Original publisher: [Read original article]() Published: 2025-05-01T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard containers](), [migration](), [Dockerfile](), [Open Source](), [Command-line interface]() Tags: [chainguard-containers](), [cli](), [containers](), [debian](), [dockerfile-converter](), [dockerfiles](), [env-file-security](), [migration](), [open-source](), [redhat-ubi]() ### AI overview Chainguard announces Dockerfile Converter, an open source CLI tool that helps developers migrate Dockerfiles to Chainguard Containers. It automates parts of the conversion process, reducing manual effort, configuration mistakes, and troubleshooting during adoption across teams. The local tool operates offline and converts image and package references, users, syntax differences, and entry points for the Chainguard ecosystem. ### Source excerpt Dockerfile Converter is a new open source tool designed to reduce the manual toil engineers go through when migrating to Chainguard Containers. ## Efficient Dockerfile templating for complex build scenarios DevFeed: [Efficient Dockerfile templating for complex build scenarios]() Original publisher: [Read original article]() Author: Tom Published: 2025-01-01T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Dockerfile](), [Docker](), [Docker Image](), [configuration]() Tags: [alpine](), [base-images](), [best-practices](), [build](), [dependencies](), [devops](), [docker](), [docker-base-images](), [dockerfiles](), [go](), [infra](), [java](), [linux](), [scm](), [sre](), [ubuntu]() ### AI overview This article explains why Dockerfile templating can help maintain complex Docker base-image variants. It discusses combinations of operating systems, Tomcat versions, Java versions, configurations, and package names, along with the differing responsibilities of development and infrastructure teams. ### Source excerpt Why even consider templating Dockerfiles? Dockerfiles revolutionized the industry with their simplicity. Each instruction creates a new layer in the image, which is automatically cached. This process integrates well with SCM, where you "commit" the results of one stage and move forward with other changes. The process can be easily parameterized with ARG instructions, similar to ENV but provided during the build. This allows for creating highly flexible builds. For most users, this is more than sufficient. However, there's a notable exception: Docker base images. ## How to transition to secure container images with new migration guides DevFeed: [How to transition to secure container images with new migration guides]() Original publisher: [Read original article]() Published: 2024-05-22T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [migration](), [container images](), [container-security](), [APK](), [Dockerfile](), [Package manager](), [Bash](), [Zsh](), [Debian]() Tags: [and-best-practices](), [apk](), [base-images](), [bash](), [best-practices](), [build](), [chainguard](), [chainguard-images](), [container](), [container-based-application](), [container-images](), [container-security](), [container-security-strategy](), [cves](), [debian](), [dependencies](), [docker-hub-image](), [dockerfiles](), [guides](), [how-to](), [image-migration](), [migration](), [migration-guides](), [python-image](), [secure-container-image](), [secure-container-images]() ### AI overview This guide explains how to migrate container images to Chainguard Images for smaller image sizes, fewer vulnerabilities, and continuous maintenance. It covers using -dev images for shells and package managers, installing bash or zsh when needed, searching for packages with apk, and adapting Dockerfiles and entrypoint scripts. ### Source excerpt Struggling to adopt secure container images? Our new migration guides provide step-by-step instructions and best practices for a smooth transition. ## How old are Official Docker images? 2024 Edition DevFeed: [How old are Official Docker images? 2024 Edition]() Original publisher: [Read original article]() Author: Tom Published: 2024-03-24T00:00:00Z Content type: article Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [docker images](), [Docker Hub](), [centos](), [Debian](), [Ubuntu](), [openjdk](), [Bash](), [Script](), [deprecated]() Tags: [bash](), [centos](), [centos-docker-image](), [debian](), [debian-docker-image](), [deprecated](), [docker](), [docker-hub](), [docker-image-age](), [docker-image-updates](), [docker-images](), [dockerfiles](), [eclipse](), [end-of-life](), [images](), [official-docker-images](), [openjdk](), [script](), [ubuntu](), [ubuntu-docker-image]() ### AI overview An analysis of the age and update status of official Docker images in 2024. It reports that modern OS images are generally reasonably current, while CentOS and OpenJDK images have reached important lifecycle or maintenance milestones. ### Source excerpt Discover the current age and update status of various official Docker images, including CentOS, Ubuntu, and Debian, in the 2024 edition of this analysis. ## Best practices for writing Dockerfiles - Follow "Filesystem Hierarchy Standard" DevFeed: [Best practices for writing Dockerfiles - Follow "Filesystem Hierarchy Standard"]() Original publisher: [Read original article]() Author: Tom Published: 2024-03-11T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Dockerfile](), [Filesystems](), [Docker Image](), [Containers](), [maintenance]() Tags: [best-practices](), [containers](), [docker](), [docker-container-maintainability](), [docker-image](), [docker-image-organization](), [dockerfile-best-practices](), [dockerfiles](), [fhs-guidelines](), [filesystem-hierarchy-standard](), [linux](), [maintainability](), [volumes]() ### AI overview This tutorial explains how to organize Docker images according to the Filesystem Hierarchy Standard. It covers locations for scripts, binaries, Java artifacts, web content, and temporary or writable files, recommending volumes for files that containers must write. ### Source excerpt Learn best practices for writing Dockerfiles by following the Filesystem Hierarchy Standard (FHS) to enhance organization and maintainability of your Docker images. ## netlab 1.8.0: Control-Plane Daemons, BIRD, dnsmasq DevFeed: [netlab 1.8.0: Control-Plane Daemons, BIRD, dnsmasq]() Original publisher: [Read original article]() Published: 2024-03-04T07:25:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [BGP](), [DHCP](), [Docker](), [Containers](), [Ubuntu](), [Cisco]() Tags: [bgp](), [cisco](), [container](), [container-image](), [dhcp](), [docker](), [dockerfiles](), [netlab](), [networking](), [ospf](), [ubuntu]() ### AI overview This release article describes netlab 1.8.0, which adds control-plane daemon support through BIRD for OSPF and BGP and dnsmasq for DHCP. It also explains building required BIRD container images with Dockerfiles and the netlab clab build command, and lists additional networking, validation, configuration, and startup features. ### Source excerpt I wanted to include open-source networking-related software into netlab topologies since (at least) the days I was writing the DHCP relaying saga. It turned out to be a bit more complex than I anticipated (more about that in another blog post), but I hope you'll find it useful. netlab release 1.8.0 includes dnsmasq running as a DHCP server and BIRD running OSPF and BGP. ExaBGP and GoBGP are already on the wish list; if you have any other ideas, please start a GitHub discussion. I had a hard time finding reasonable container images for BIRD; the BIRD team does not publish them, and everything else I found looked either abandoned or a hobby project. The solution turned out to be exceedingly simple: you cannot run the containers without Docker anyway, which means the docker build command is just a few keystrokes away. I added Dockerfiles needed to build those containers to the netlab source code and implemented the netlab clab build command as a thin wrapper around docker build. It takes just a few seconds (plus the time it takes to download the Ubuntu container image) to build the containers you need. Read more ... ## Automatic updates of Docker images with Renovate Bot DevFeed: [Automatic updates of Docker images with Renovate Bot]() Original publisher: [Read original article]() Author: Tom Published: 2024-03-01T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [Dockerfile](), [renovate](), [configuration]() Tags: [automate-docker-updates](), [bash](), [best-practices](), [dependencies](), [dependency](), [developers](), [devops](), [devops-best-practices](), [docker](), [docker-image-updates](), [docker-security](), [dockerfiles](), [how-to](), [linux](), [renovate](), [renovate-bot](), [renovate-vs-dependabot](), [security](), [updates]() ### AI overview A practical guide to automating Docker image and dependency updates with Renovate Bot. It explains how Renovate detects parent image changes, tracks binaries downloaded from sources such as GitHub or Maven, and uses custom comments and configuration to identify dependencies and propose or automatically merge updates. ### Source excerpt Learn how to automate Docker image updates using Renovate Bot, a versatile tool that supports various package managers and custom dependency links. ## Building minimal and low CVE images for compiled languages DevFeed: [Building minimal and low CVE images for compiled languages]() Original publisher: [Read original article]() Published: 2024-02-27T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Containers](), [Docker](), [Dockerfile](), [Go Language](), [Vulnerabilities](), [Docker Hub](), [Debian](), [Ubuntu]() Tags: [chainguard](), [chainguard-images](), [compiled-language](), [containers](), [deployment](), [distroless](), [docker](), [docker-hub](), [dockerfiles](), [dockerhub](), [go](), [vulnerabilities]() ### AI overview This article demonstrates how to build smaller, lower-CVE container images for compiled languages by separating build and runtime concerns and replacing full Debian or Ubuntu bases with Chainguard Images. A Go web server example reduces the image from 892 MB to 775 MB and eliminates the reported CVEs after a one-line base-image change. ### Source excerpt Leverage Chainguard's insights to forge low-CVE, compact images for compiled languages, boosting your security posture. ## Keep your Chainguard Images up to date with digestabot DevFeed: [Keep your Chainguard Images up to date with digestabot]() Original publisher: [Read original article]() Published: 2023-12-18T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [chainguard](), [GitHub Actions](), [Pull Request](), [Security]() Tags: [also](), [chainguard](), [chainguard-images](), [container](), [continuous-integration](), [digestabot](), [dockerfiles](), [github-action](), [helm](), [make](), [merge](), [oidc](), [security](), [vulnerability-automation](), [vulnerability-management]() ### AI overview Chainguard's digestabot is a free GitHub Action that helps keep Chainguard Images and other container assets current. It detects outdated image digests, opens pull requests, and supports testing and secure updates through continuous integration and optional ephemeral OIDC tokens. ### Source excerpt Experience hassle-free updates with Chainguard's digestabot, ensuring your Images stay secure and up-to-date daily. ## Buildpacks - 3 months later DevFeed: [Buildpacks - 3 months later]() Original publisher: [Read original article]() Author: Domenico Luciani Published: 2023-11-15T23:00:00Z Content type: opinion Language: en Sources: [Domenico Luciani]() Topics: [Buildpacks](), [Open Source](), [Containers](), [Cloud Native Ecosystem]() Tags: [buildpacks](), [cloud-native](), [container-image](), [containers](), [dependencies](), [dockerfiles](), [oci](), [open-source](), [optimize](), [use-cases]() ### AI overview The author recounts spending three months on VMware's CNB--Cloud Native Buildpacks--team through the company's Take3 initiative. The article explains that Buildpacks turn source code into OCI-compliant container images, manage dependencies and runtimes, and use separate layers that can be updated independently. ### Source excerpt Since the beginning of my career in this industry, I've always been fascinated by the open-source world. After so many years of contributing on my own, this year, I finally joined... ## Chainguard's image tagging philosophy: enabling high velocity updates (pt. 1 of 3) DevFeed: [Chainguard's image tagging philosophy: enabling high velocity updates (pt. 1 of 3)]() Original publisher: [Read original article]() Published: 2023-11-13T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Vulnerabilities](), [releases]() Tags: [chainguard](), [chainguard-images](), [container-image](), [cve](), [distro](), [dockerfiles](), [github](), [image-tagging](), [series](), [software-security-practices](), [velocity]() ### AI overview Part 1 explains Chainguard's image-tagging philosophy for delivering fast updates while keeping image identities clear and usable. It describes epoch-based package revisions, vulnerability fixes, and how updates to packages within multi-package images can be delivered without changing the upstream version. ### Source excerpt Explore Part 1 of Chainguard's image tagging philosophy series, focusing on enabling high-velocity updates. ## Unlocking efficiency and security on GitLab: On-demand images with 0-CVE packages powered by Wolfi DevFeed: [Unlocking efficiency and security on GitLab: On-demand images with 0-CVE packages powered by Wolfi]() Original publisher: [Read original article]() Published: 2023-10-30T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [GitLab](), [CI/CD](), [Docker](), [Kubernetes]() Tags: [ci-cd](), [cicd](), [container-images](), [containers](), [dockerfiles](), [efficiency](), [gitlab](), [kubernetes](), [security](), [wolfi]() ### AI overview This tutorial explains how to integrate the wolfi-act project with GitLab CI/CD, focusing on Docker and Kubernetes executors and on-demand images with 0-CVE packages powered by Wolfi. ### Source excerpt Experience secure, efficient GitLab operations with 0-CVE on-demand images, fueled by Wolfi OS. ## How to use Dockerfiles with wolfi-base images DevFeed: [How to use Dockerfiles with wolfi-base images]() Original publisher: [Read original article]() Published: 2023-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [Dockerfile](), [Docker](), [chainguard images](), [distroless](), [container images](), [Linux](), [Go]() Tags: [apko](), [base-images](), [chainguard-images](), [container-images](), [distroless](), [docker](), [docker-hub](), [dockerfiles](), [go](), [guide](), [how-to](), [melange](), [wolfi]() ### AI overview This tutorial explains how to use Dockerfiles with Chainguard wolfi-base and other Chainguard Images. It covers minimal static images, glibc-dynamic images, multi-stage builds, package management, and selecting image variants based on application dependencies and runtime needs. ### Source excerpt Your guide to leveraging Dockerfiles with Wolfi-base images for hardened container images. ## Alternatives to Dockerfiles for Crafting Container Images DevFeed: [Alternatives to Dockerfiles for Crafting Container Images]() Original publisher: [Read original article]() Published: 2023-04-27T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Containers](), [Dockerfile](), [Docker](), [Security]() Tags: [chainguard-images](), [containers](), [docker](), [dockerfiles](), [security](), [security-vulnerabilities](), [vulnerability-management]() ### AI overview This article examines drawbacks of Dockerfiles for building container images, including security concerns, performance issues, image bloat, and reliance on online build services. It surveys alternatives such as ko, Bazel, Nix, and apko, comparing their strengths and weaknesses and discussing how to choose and migrate to an approach. ### Source excerpt Creating Docker images can sometimes be a pain. Here are alternatives for crafting containers, like ko, Bazel, Nix, and apko, and their strengths and weaknesses ## Docker Best Practices - Use VOLUME for temporary and mutable files DevFeed: [Docker Best Practices - Use VOLUME for temporary and mutable files]() Original publisher: [Read original article]() Author: Tom Published: 2022-09-12T00:00:00Z Content type: article Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [Dockerfile]() Tags: [best-practices](), [docker](), [docker-container-performance](), [docker-image-maintenance](), [docker-image-optimization](), [docker-volume-usage](), [dockerfile-best-practices](), [dockerfiles](), [performance](), [temporary-file-locations-docker](), [volume](), [volumes]() ### AI overview The article recommends using Dockerfile VOLUME declarations for temporary and mutable file locations. It explains that volumes are separate from layered image filesystems, can improve performance, and help keep images clean, while noting that unused anonymous volumes require periodic cleanup. ### Source excerpt Learn best practices for writing Dockerfiles by using VOLUME for all mutable, temporary file locations to enhance performance and maintain cleaner images. ## Docker Best Practices - Use .dockerignore DevFeed: [Docker Best Practices - Use .dockerignore]() Original publisher: [Read original article]() Author: Tom Published: 2022-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [build times](), [context]() Tags: [best-practices](), [build](), [build-times](), [docker](), [docker-build-context](), [docker-build-optimization](), [docker-image-efficiency](), [dockerfile-best-practices](), [dockerfiles](), [dockerignore-usage](), [exclude-files-docker]() ### AI overview This tutorial explains that Docker uploads the entire build context to the Docker daemon during an image build. It recommends using a .dockerignore file to exclude unnecessary sources, test results, and other working-directory files, which can help reduce build times. ### Source excerpt Learn best practices for writing Dockerfiles by using .dockerignore to optimize build times and exclude unnecessary files from the build context. ## Dockerfile writing best practices DevFeed: [Dockerfile writing best practices]() Original publisher: [Read original article]() Author: Tom Published: 2022-09-10T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Dockerfile](), [Docker](), [docker images](), [Security]() Tags: [best-practices](), [docker](), [docker-container-security](), [docker-image-maintenance](), [docker-image-optimization](), [docker-multi-stage-builds](), [docker-volume-usage](), [dockerfile-best-practices](), [dockerfiles](), [how-to]() ### AI overview The article introduces a planned series on Dockerfile writing best practices, based on the author's experience preparing containers for company applications. Planned topics include .dockerignore, filesystem standards, package cleanup, volumes, non-root execution, multi-stage builds, image labels, security scanning, and build cache. ### Source excerpt Learn best practices for writing Dockerfiles to create efficient, secure, and maintainable Docker images, based on real-world experience and insights. ## Treating Dockerfiles as shell scripts DevFeed: [Treating Dockerfiles as shell scripts]() Original publisher: [Read original article]() Published: 2020-12-03T00:00:00Z Content type: tutorial Language: en Sources: [Jake Wharton]() Topics: [Dockerfile](), [Docker](), [Containers](), [Scripting, bash](), [Command-line interface](), [Tool]() Tags: [bash](), [chmod](), [containers](), [docker](), [dockerfiles](), [implementation](), [tools](), [usability]() ### AI overview The article presents a utility that lets executable Dockerfiles behave like shell scripts. A shebang invokes a helper that conditionally runs docker build and then docker run, improving the edit-and-run workflow for containerized tools. ### Source excerpt I use Docker to run a lot of tools. With the tools all wrapped up in containers, my computers are free of Python and Go and the various other dependencies needed for their use. While this is a nice win for isolation and reproducibility, the user experience is sub-par. To run a tool, I just use docker run: $ docker run --rm tool arguments... But the editing workflow is something like: $ nano tool.dockerfile # hack hack hack... $ docker build -t tool - < tool.dockerfile $ docker run --rm tool arguments... I also use a lot of bash scripts with easy-to-remember names. To run a script I just type its name: ./update_containers.sh. To edit, I open it in an editor, save, and then run. The user experience of this is top-notch! Can we combine the two? Executable Dockerfiles If the first line of an executable starts with #!, unix-y systems will treat what follows on that line as an executable for interpreting the rest of the file. This is called the shebang, and the bash scripts I use start with one: #!/usr/bin/env bash. In order to do this with a Dockerfile, though, we need a program which will conditionally run docker build and then docker run the resulting image. Thankfully docker build is already conditional and won't rebuild anything unless necessary, so we can always run it. #!/usr/bin/env bash NAME=$(basename "$1") docker build -t "$NAME" - < "$1" > /dev/null shift # Remove script name from arguments docker run --rm --name "$NAME" "$NAME" "$@" With this saved as dockerfile-shebang.sh, we can add it as the shebang in a Dockerfile. #!/path/to/dockerfile-shebang.sh FROM alpine:latest ENTRYPOINT ["echo"] Saving this as echo.dockerfile and running chmod +x echo.dockerfile provides the user experience we're after: $ ./echo.dockerfile Hello, world! Hello, world! It's Dockerfile-Shebang! I have wrapped up this utility into an executable, dockerfile-shabang. You can find it at github.com/JakeWharton/dockerfile-shebang. The implementation is a bit more complicated than above for ## Portable Development Environment With Docker and IntelliJ DevFeed: [Portable Development Environment With Docker and IntelliJ]() Original publisher: [Read original article]() Author: mateusz-joniak Published: 2018-10-15T00:00:00Z Content type: tutorial Language: en Sources: [Backend Development on nexocode]() Topics: [Docker](), [Dockerfile](), [Development](), [virtualization](), [ide](), [IntelliJ IDEA]() Tags: [configuration](), [development](), [docker](), [dockerfiles](), [ide](), [intellij](), [intellij-idea](), [software](), [virtualization]() ### AI overview This tutorial explains how Docker can create portable development environments by packaging an application with its dependencies, configuration files, tools, and runtime. It describes Docker images and Dockerfiles, and presents using the same image across developer workstations and production to reduce configuration differences and deployment surprises. ### Source excerpt For many developers, managing the environment required to work productively is a quite tedious task. Sure, the IDE does the lion's share of preparations for you. But still, you need to install a specific version of the database, then make sure you have the right compiler and runtime environment. In some cases, you would also have to work on a given version of the operating system. Gods help you if you find yourself in the hell of "hidden" dependencies, like libraries you're supposed to have installed separately. Configuring all of this takes hours, so forget about first-day productivity, and if you fail, all you're going to get are some cryptic error messages that you have to type into Google. Sounds familiar? [Next page]()