# docker images Published articles for docker images. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Docker Hodgepodge Images DevFeed: [Docker Hodgepodge Images]() Original publisher: [Read original article]() Published: 2026-04-15T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Docker Hardened Images](), [supply-chain-security](), [vulnerability](), [Docker]() Tags: [chainguard-vs-docker](), [dhi](), [docker](), [docker-containers](), [docker-hardened-images](), [docker-images](), [free-container-images](), [security](), [supply-chain-security](), [vulnerability](), [vulnerability-scanner]() ### AI overview The article argues that Docker Hardened Images are Debian Trixie derivatives rather than ordinary Debian images. It contends that Docker's custom repository, rebuilt packages, and operating-system identification can cause vulnerability scanners and related tools to produce inaccurate results, creating supply chain security concerns. ### Source excerpt Docker ships their own Linux distro, they just pretend not to. Learn how misidentification and VEX usage can mislead scanners and impact supply chain security. ## Why Trusted Software Supply Chains Matter More Than Zero-CVE Container Claims DevFeed: [Why Trusted Software Supply Chains Matter More Than Zero-CVE Container Claims]() Original publisher: [Read original article]() Published: 2026-01-15T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Security](), [container-security](), [container images](), [Docker Hub](), [Containers](), [Docker](), [Software]() Tags: [ceo](), [chainguard](), [chainguard-containers](), [chainguard-images](), [chainguard-libraries](), [container-images](), [docker](), [docker-hub](), [docker-images](), [echo-security](), [hardened-images](), [hardening](), [minimus](), [rapidfort](), [secure-by-default](), [security](), [software-supply-chain-security](), [wiz-images](), [zero-cves]() ### AI overview Chainguard CEO Dan Lorenc argues that container security depends on trusting the origins and build processes of software, rather than relying primarily on post-hoc image hardening or zero-CVE claims. ### Source excerpt Chainguard CEO Dan Lorenc explains why real security comes from trusted, from-source software supply chains, not post-hoc hardening or zero-CVE promises. ## Squashing Docker images with Buildx DevFeed: [Squashing Docker images with Buildx]() Original publisher: [Read original article]() Author: Tom Published: 2025-12-24T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [docker images](), [Dockerfile](), [Caching]() Tags: [best-practices](), [build](), [build-system](), [caching](), [devops](), [docker](), [docker-buildx](), [docker-image-optimization](), [docker-images](), [docker-layer-management](), [dockerfile-best-practices](), [linux](), [squash-docker-image]() ### AI overview This tutorial explains how to create smaller Docker images with Buildx by rebuilding the final filesystem state into a new image, removing intermediate layers. It also discusses the trade-off: this approach can prevent reuse of base-image layer caching, while selectively copying files follows a builder-pattern alternative. ### Source excerpt Learn how to squash Docker images using Buildx to create smaller, more efficient images by consolidating layers. ## Optimize Docker Images: Faster Builds, Smaller Size DevFeed: [Optimize Docker Images: Faster Builds, Smaller Size]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-08-24T00:00:00Z Content type: tutorial Language: en Sources: [Abhimanyu Saharan]() Topics: [Docker](), [Docker Image](), [Caching]() Tags: [best-practices](), [cache](), [caching](), [docker](), [docker-images](), [how-to](), [reduce](), [speed]() ### AI overview A tutorial on optimizing Docker images by reducing image size and speeding up builds through smart caching, cache busting, multi-stage builds, and BuildKit best practices. ### Source excerpt Learn how to reduce Docker image size and speed up builds with smart caching, cache busting, multi-stage builds, and BuildKit best practices. ## Fork yeah: We're bringing kaniko back DevFeed: [Fork yeah: We're bringing kaniko back]() Original publisher: [Read original article]() Published: 2025-06-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Open Source](), [supply-chain-security](), [container-security](), [Docker](), [Kubernetes]() Tags: [chainguard](), [container](), [container-security](), [deprecated](), [docker](), [docker-images](), [fork](), [google](), [kaniko](), [kubernetes](), [maintenance](), [open-source](), [safe-source-for-open-source](), [software-supply-chain]() ### AI overview Chainguard is forking and taking over maintenance of Kaniko after Google announced plans to archive it. The project will remain open and upstream, with a focus on maintenance and minor bug fixes rather than new features, while Chainguard also offers commercial Kaniko images for organizations needing zero-CVE or FIPS versions. ### Source excerpt Chainguard is taking over the maintenance of the Kaniko project, recently deprecated by Google. Learn more about why we're doing it and what is next. ## Blog: Introducing Falco 0.40.0 DevFeed: [Blog: Introducing Falco 0.40.0]() Original publisher: [Read original article]() Published: 2025-01-28T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Docker](), [Processes](), [Usability](), [Security]() Tags: [bug-fixes](), [docker](), [docker-images](), [falco](), [improvements](), [new-features](), [performance](), [process](), [release](), [version](), [x86-64]() ### AI overview Falco 0.40.0 introduces streamlined Docker images, a reintroduced static x86_64 build using musl, process metadata filters, support for sendmmsg and recvmmsg syscall parameters, and plugin-suggested output fields. The release also includes performance, usability, and bug-fix improvements, along with breaking changes for upgraders. ### Source excerpt Dear Falco Community, today we are happy to announce the release of Falco 0.40.0! This version brings several new features, performance improvements, and bug fixes that streamline Falco's detection capabilities. During this release cycle, we merged more than 52 PRs on Falco and more than 150 PRs for libs and drivers, version 0.20.0 and version 8.0.0 respectively. Thank you to our maintainers and contributors, as this would not happen without your support and dedication! To learn all about these changes, read on! What's new? TL;DR Key features: Streamlined Falco docker images; Falco static build has been reintroduced for x86_64 binary using musl; New process filters allow to filter events based on process metadata; Added support for sendmmsg and recvmmsg syscalls parameters; Plugins suggested output fields are now available in the Falco engine; This release also comes with breaking changes that you should be aware of before upgrading. Major features and improvements The 0.40.0 release contains a number of features and UX improvements. Here is a list of some of the key new capabilities. Streamlined Falco docker images In the Falco 0.40.0 release, the Falco team has streamlined the Docker images to improve usability and performance. The new images are designed to be more efficient and easier to use, providing a better experience for users deploying Falco in containerized environments. Key improvements include: Reduced Image Size: The new images are smaller, which reduces the time required to pull and deploy them. Optimized Layers: The layers in the Docker images have been optimized to improve build times and caching efficiency. Enhanced Security: The images have been hardened to enhance security, reducing potential vulnerabilities. These changes make it easier to deploy and manage Falco in various environments. Introducing new process filters A new set of process filters are made available in this release: proc.pgid, proc.pgid.name, proc.pgid.exe, proc.pgid.exepath, pr ## Installing Oracle Instant Client on Ubuntu 24.04 DevFeed: [Installing Oracle Instant Client on Ubuntu 24.04]() Original publisher: [Read original article]() Author: Tom Published: 2024-04-17T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Ubuntu](), [docker images](), [Docker](), [Containers]() Tags: [debian](), [debian-oracle-client](), [docker](), [docker-images](), [glibc](), [how-to](), [install](), [install-oracle-client](), [linux](), [linux-database-tools](), [oracle-client-docker](), [oracle-instant-client](), [ubuntu](), [ubuntu-24-04]() ### AI overview A tutorial on installing Oracle Instant Client on Ubuntu and Debian, presenting the recommended ZIP-package approach and an alternative RPM-based approach. It focuses on Docker image workflows and discusses library paths, linker cache configuration, package compatibility, and central package repositories. ### Source excerpt Learn how to install Oracle Instant Client on Ubuntu 24.04 using both recommended and alternative methods, with a focus on Docker images. ## 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. ## How to run x86-64 Docker images on Apple's MacBook with M1/M2/M3 CPU DevFeed: [How to run x86-64 Docker images on Apple's MacBook with M1/M2/M3 CPU]() Original publisher: [Read original article]() Author: Tom Published: 2024-02-06T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [docker images](), [cpu](), [virtualization]() Tags: [docker](), [docker-cross-platform](), [docker-default-platform](), [docker-images](), [mac](), [macbook-m1-docker](), [macbook-m2-docker](), [macbook-m3-docker](), [macos](), [net-11](), [terminal](), [virtualization](), [x86-64](), [x86-64-docker-images]() ### AI overview A tutorial explains how to run x86-64 Docker images on Apple MacBooks with M1, M2, or M3 CPUs by setting the DOCKER_DEFAULT_PLATFORM environment variable. It notes that this uses virtualization and is slower than native execution. ### Source excerpt Learn how to run x86-64 Docker images on Apple's MacBook with M1/M2/M3 CPUs by setting the DOCKER_DEFAULT_PLATFORM environment variable. ## Using JLink to create smaller Docker images for your Spring Boot Java application DevFeed: [Using JLink to create smaller Docker images for your Spring Boot Java application]() Original publisher: [Read original article]() Author: Brian Vermeer Published: 2023-08-24T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Docker](), [Spring Boot](), [Java](), [Docker Image](), [Application Security](), [Application Development](), [Deployment]() Tags: [acquisition](), [application-security](), [awareness](), [blog](), [blog-post](), [command-line](), [container-security](), [containers](), [deployment](), [developer](), [devrel](), [docker](), [docker-images](), [java](), [jdk](), [modules](), [performance](), [snyk-container](), [spring-boot]() ### AI overview This article explains how to use JLink with Docker to create smaller custom Java runtime images for Spring Boot and other Java applications. It describes how reducing the runtime to the modules and dependencies required by the application can lower image size, improve deployment performance, reduce storage costs, and limit container attack surface. ### Source excerpt In this blog post, we'll present an in-depth exploration of utilizing JLink to optimize Docker image sizes, enhancing application security and performance. ## The zero CVE challenge: Can official Docker Hub images pass the test? DevFeed: [The zero CVE challenge: Can official Docker Hub images pass the test?]() Original publisher: [Read original article]() Published: 2023-08-03T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Docker](), [Docker Hub](), [container-security](), [Vulnerabilities](), [Debian](), [Containers](), [grype]() Tags: [container-security](), [cve](), [cves](), [debian](), [docker](), [docker-hub](), [docker-hub-image](), [docker-images](), [grype](), [image-cves](), [security](), [software](), [vulnerabilities]() ### AI overview An analysis of ten widely used official Docker Hub images found that updating all operating-system packages reduced vulnerability counts by less than 6% on average. Approximately 98% of the vulnerabilities were associated with Debian-based packages, and the average image still had 225 vulnerabilities after updates. ### Source excerpt Uncover the findings of the Zero CVE Challenge on Official Docker Hub Images, a step towards secure containerization. ## GoReleaser Split and Merge DevFeed: [GoReleaser Split and Merge]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2022-11-12T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [builds](), [GitHub Actions](), [configuration](), [Caching](), [Windows](), [docker images]() Tags: [builds](), [cache](), [configuration](), [docker-images](), [github-actions](), [pipeline](), [windows](), [workflow]() ### AI overview This tutorial explains how GoReleaser can split and merge its release process so builds for different platforms run on separate machines before their results are merged and published. It demonstrates an example pipeline using GitHub Actions, artifacts, and the cache, and discusses CGO and Windows Docker image builds. ### Source excerpt Since v1.12.0-pro, GoReleaser can split and merge its release process. ## How to setup remote docker host DevFeed: [How to setup remote docker host]() Original publisher: [Read original article]() Published: 2022-09-26T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Docker](), [Image](), [docker images](), [Testcontainers](), [Amazon EC2](), [Amazon Web Services](), [Linux](), [TLS (Transport Layer Security)](), [x86]() Tags: [arm](), [aws](), [containers](), [docker](), [docker-images](), [ec2](), [how-to](), [integration-test](), [linux](), [remote](), [tls](), [x86]() ### AI overview This tutorial explains how to set up a remote Docker host for integration tests when required ARM images are unavailable. It uses a Linux x86_64 AWS EC2 machine, configures TLS access to the Docker daemon, and connects a local Docker client to the remote host. ### Source excerpt Not all docker images are available for ARM architecture (hopefully this will improve over time). Right now I'm working on a project where images for ARM are not available. Emulation works ok (but slow) most of the time. Lately, I stumbled upon an interesting performance/startup issue when running amd64-based containers using testcontainers in an integration test. Read more ## Enabling Nightly releases using GoReleaser Pro DevFeed: [Enabling Nightly releases using GoReleaser Pro]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2022-08-28T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [releases](), [GitHub Actions](), [Docker]() Tags: [added](), [docker](), [docker-images](), [github-actions](), [releases](), [support](), [v1](), [workflow]() ### AI overview A tutorial on configuring GoReleaser Pro v1.11 or later to maintain a single nightly release, including nightly Docker image handling and GitHub Actions automation. ### Source excerpt GoReleaser Pro v1.11+ added support to keeping a nightly release. ## Multi-platform Docker images with GoReleaser, Podman and GitHub Actions DevFeed: [Multi-platform Docker images with GoReleaser, Podman and GitHub Actions]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-08-01T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Docker](), [podman](), [GitHub Actions](), [Docker Hub](), [GitHub Container Registry](), [personal access token]() Tags: [distribution](), [docker](), [docker-images](), [github-actions](), [github-container-registry](), [manifest](), [personal-access-token](), [podman]() ### AI overview A tutorial showing how to build and publish multi-platform container images with GoReleaser, Podman, and GitHub Actions. It explains rootless, daemonless Podman usage, multi-platform builds and manifests, GitHub Container Registry authentication with a personal access token, and release automation. ### Source excerpt A few months ago, I published a post on Multi-platform Docker images with GoReleaser and GitHub Actions. Today's post has the same idea, but using Podman instead of Docker. ## GoReleaser: 4 years releasing software DevFeed: [GoReleaser: 4 years releasing software]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-01-07T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [Software](), [Go](), [GitHub Actions](), [docker images](), [MkDocs](), [Refactoring](), [reproducible builds](), [parquet](), [Pull Request]() Tags: [apple-silicon](), [compression](), [docker-images](), [github-actions](), [go](), [hooks](), [linux](), [refactoring](), [reproducible-builds](), [software]() ### AI overview A four-year retrospective on GoReleaser describes improvements made over the previous year, including deprecated-setting removal, package signing and creation, build hooks, compression, shell completions, GitHub Actions migration, reproducible builds, and multi-architecture Docker image support. It also notes an Apple Silicon support pull request awaiting the Go 1.16 release. ### Source excerpt Last year, I made a blog post about GoReleaser turning 3 years old. ## Vouching for Docker Images DevFeed: [Vouching for Docker Images]() Original publisher: [Read original article]() Author: Cat Jones Published: 2020-12-01T15:00:01Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Docker](), [Containers](), [Security, Privacy and Abuse Prevention](), [Cryptography](), [Kubernetes](), [Open Source]() Tags: [containers](), [cryptography](), [docker](), [docker-images](), [kubernetes](), [open-source](), [verification]() ### AI overview The article explains how code signing and Binary Authorization can protect Docker images from tampering and malicious software in Kubernetes environments. It introduces Voucher, an open source Shopify project intended to apply these protections without requiring developers to learn cryptography. ### Source excerpt If you were using computers in the '90s and the early 2000s, you probably had the experience of installing a piece of software you downloaded from the internet, only to discover that someone put some nasty into it, and now you're dragging your computer to IT to beg them to save your data. To remedy this, software developers started "signing" their software in a way that proved both who they were and that nobody tampered with the software after they released it. ## Geth security release DevFeed: [Geth security release]() Original publisher: [Read original article]() Author: Geth team Published: 2020-11-12T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Go Language](), [Security](), [Vulnerabilities](), [releases](), [docker images](), [Algorithm]() Tags: [cve](), [docker](), [docker-images](), [ethereum](), [go](), [golang](), [release](), [release-notes](), [security](), [vulnerability]() ### AI overview This security release warns that Geth versions built with vulnerable Go versions may be affected by CVE-2020-28362, a denial-of-service flaw capable of crashing nodes during block processing. It recommends rebuilding with Go 1.15.5 or 1.14.12, ideally as Geth v1.9.24, and discusses related release coordination and an ethash mining issue. ### Source excerpt ... ## Deploys at Gamechanger DevFeed: [Deploys at Gamechanger]() Original publisher: [Read original article]() Author: GameChanger Published: 2020-07-28T22:24:51Z Content type: article Language: en Sources: [GameChanger]() Topics: [Deployment](), [Docker](), [Amazon EC2](), [ci](), [Dockerfile](), [Docker Image](), [Protocol (disambiguation)]() Tags: [build](), [ci](), [container](), [deployment](), [docker](), [docker-images](), [images](), [load-balancer](), [protocol]() ### AI overview This article describes GameChanger's deployment pipeline. Each commit triggers CI to build and tag a Docker image, push it to an internal Docker registry, and deploy it to relevant Amazon EC2 instances. The instances start containers, register with a load balancer, and receive deployment notifications through Serf's Gossip protocol. ### Source excerpt At GameChanger, being able to deploy our changes quickly and reliably has always been important. Over the past few months on the platform team, we've been working to build a simpler and more reliable deployment pipeline to support our product teams in shipping code with speed and reliability. In this post, I'll go over the system that we have in place now, and some of our recent improvements. How deploys our work High Level Overview At a high level, the core of our deployment process involves shipping a docker image to some EC2 instances, and then starting a container with that image. Our main code repository contains a Dockerfile with the required configuration for our live app. After each new commit to our main code repository, Our CI process will docker build a new image with a new tag, and push it to our internal docker registry. During a deploy, we pull that image on the relevant EC2 instances, and start a container with it. Once we have a running container, we register that EC2 instance with a load balancer, and start serving traffic. While the high level is straight forward, there's a lot of work that goes into making sure our deployments happen safely, and at the right time. Once a new image has been pushed to our registry by our CI process, we need to notify all our currently running instances that there's a new version to deploy. Each commit corresponds to a new docker tag that's created during the build. Once the tag is created, we notify our internal deployment service of the new version. Once our tag is pushed, and our deployment service is aware of it, we tell our deployment service to start a deploy, which will send a message to all of our running EC2 instances. Serf Messages We use Serf to send that message out without needing to directly contact every instance. The message we send contains a role and environment. The role is the name of a docker image we want to deploy a new version of, and environment will be production or staging depending on wher ## Docker Images : Part III - Going Farther To Reduce Image Size DevFeed: [Docker Images : Part III - Going Farther To Reduce Image Size]() Original publisher: [Read original article]() Published: 2020-04-03T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Docker](), [Docker Image](), [Optimization](), [Dockerfile](), [Containers](), [systems]() Tags: [ardan-labs](), [base-images](), [bazel](), [blog](), [build](), [building](), [cache](), [containers](), [docker](), [docker-image](), [docker-images](), [drivers](), [files](), [go](), [go-programming](), [golang](), [how-to](), [image](), [images](), [memory](), [network](), [optimization](), [programming](), [reduce](), [systems]() ### AI overview The third article in a series on reducing Docker image size explains further optimization techniques, including standardized base images, stripped binaries, asset optimization, and tools such as DockerSlim and Bazel. It also describes how shared image layers can reduce network, storage, disk I/O, and memory usage when running multiple containers. ### Source excerpt Series Index Reducing Image Size Details Specific To Different Languages Going Farther To Reduce Image Size Introduction In the first two parts of this series, we covered the most common methods to optimize Docker image size. We saw how multi-stage builds, combined with Alpine-based images, and sometimes static builds, would generally give us the most dramatic savings. In this last part, we will see how to go even farther. We will talk about standardizing base images, stripping binaries, assets optimization, and other build systems or add-ons like DockerSlim or Bazel, as well as the NixOS distribution. ## Docker Images : Part II - Details Specific To Different Languages DevFeed: [Docker Images : Part II - Details Specific To Different Languages]() Original publisher: [Read original article]() Published: 2020-02-24T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Docker](), [docker images](), [Go Language](), [Go]() Tags: [ardan-labs](), [blog](), [docker](), [docker-images](), [go](), [go-programming](), [golang](), [languages](), [programming]() ### AI overview The second part of a series on reducing Docker image size explains how Go binaries can be dynamically linked when they use system libraries through cgo. It shows that disabling cgo with CGO_ENABLED=0 produces a static binary that can run without those libraries, and introduces the netgo build tag for selecting Go's native network implementation. ### Source excerpt Series Index Reducing Image Size Details Specific To Different Languages Going Farther To Reduce Image Size Introduction In the first part, we introduced multi-stage builds, static and dynamic linking, and briefly mentioned Alpine. In this second part, we are going to dive into some details specific to Go. Then we will talk more about Alpine, because it's worth it; and finally we will see how things play out with other languages like Java, Node, Python, Ruby, and Rust. ## Docker Images : Part I - Reducing Image Size DevFeed: [Docker Images : Part I - Reducing Image Size]() Original publisher: [Read original article]() Published: 2020-02-04T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [docker images](), [Dockerfile](), [Containers](), [C](), [Go](), [Ubuntu](), [bazel]() Tags: [ardan-labs](), [base-images](), [bazel](), [blog](), [c](), [containers](), [docker](), [docker-images](), [go](), [go-programming](), [golang](), [how-to](), [programming](), [rust](), [ubuntu]() ### AI overview This tutorial explains techniques for reducing Docker image size, beginning with multi-stage builds and covering static versus dynamic linking and Alpine. It uses C and Go examples and introduces additional approaches such as common base images, stripping binaries, Bazel, Distroless, DockerSlim, and UPX, while noting that extreme reductions are not always appropriate. ### Source excerpt Series Index Reducing Image Size Details Specific To Different Languages Going Farther To Reduce Image Size Introduction When getting started with containers, it's pretty easy to be shocked by the size of the images that we build. We're going to review a number of techniques to reduce image size, without sacrificing developers' and ops' convenience. In this first part, we will talk about multi-stage builds, because that's where anyone should start if they want to reduce the size of their images. We will also explain the differences between static and dynamic linking, as well as why we should care about that. This will be the occasion to introduce Alpine. ## 1º Changelog Meetup DevFeed: [1º Changelog Meetup]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2017-11-21T00:00:00Z Content type: article Language: en Sources: [Carlos Becker]() Topics: [Go Language](), [Docker](), [docker images](), [Homebrew](), [Linux]() Tags: [build](), [docker](), [docker-images](), [go](), [homebrew](), [linux](), [meetup](), [packages](), [release]() ### AI overview A presentation covered building and releasing Go binaries, including cross-compilation, Docker images, Linux packages, and Homebrew, with GoReleaser featured at the end. ### Source excerpt I showed how to build and release binaries in Go, including cross-compiling, Docker images, Linux packages and Homebrew, featuring GoReleaser on the end. ## Some useful commands in Docker DevFeed: [Some useful commands in Docker]() Original publisher: [Read original article]() Author: Tom Published: 2016-02-11T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [Containers](), [docker images]() Tags: [build](), [commands](), [container](), [containers](), [docker](), [docker-images](), [image](), [logs](), [running](), [volumes]() ### AI overview A practical Docker tutorial listing commands for managing containers, images, and volumes, running and entering containers, viewing build logs, and building an image from the current directory. ### Source excerpt I started playing with Docker and here I will write some commands that where not so obvious at beginning 😃 List running containers: docker ps List also not running containers: docker ps -a Remove all containers (be careful with that): docker rm $(docker ps -a -q) Remove all images: docker rmi $(docker images -q) Docker won't remove any old volumes used by containers, so after some time you may be interested in deleting them all: [Next page]()