# Docker Image A standardized package containing the files, binaries, libraries, and configurations needed to run a container. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What's New in Rover: Docker Image, Schema Search, Client Checks, and More DevFeed: [What's New in Rover: Docker Image, Schema Search, Client Checks, and More]() Original publisher: [Read original article]() Author: Kaitlyn Barnard Published: 2026-07-17T11:24:07Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [GraphOS](), [Docker](), [Docker Image](), [Command-line interface](), [GitHub Container Registry](), [CI/CD](), [AI research agents]() Tags: [agents](), [announcement](), [ci-cd](), [cli](), [container-image](), [feature](), [github-container-registry](), [graphos](), [graphql]() ### AI overview Apollo's latest Rover release adds an official immutable Docker image, atomic schema check-and-publish, native client operation checks, and schema search commands for teams building AI agents. ### Source excerpt Rover's latest release adds an official Docker image, atomic check-and-publish, native client checks, and schema search for agents. ## ClickHouse on Docker Hardened Images DevFeed: [ClickHouse on Docker Hardened Images]() Original publisher: [Read original article]() Author: Karolina Ruiz Rogelj; Melvyn Peignon Published: 2026-07-10T15:28:34Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Docker Hardened Images](), [Docker](), [Security](), [Vulnerabilities](), [Docker Image](), [vulnerability](), [Ubuntu](), [apt](), [Perl](), [Amazon Web Services]() Tags: [apt](), [clickhouse](), [deployment](), [developers](), [docker](), [docker-hardened-images](), [docker-hub](), [docker-image](), [images](), [security](), [ubuntu](), [vulnerability]() ### AI overview ClickHouse is now available as a Docker Hardened Image: a minimal, security-hardened build that preserves ClickHouse behavior while shipping only the components needed to run the database and pass enterprise vulnerability scans. ### Source excerpt ClickHouse is now available as a Docker Hardened Image: a minimal, security-hardened build that passes enterprise vulnerability scans by shipping only what the database needs to run, with no change to how ClickHouse behaves. ## Scaling out Distroless adoption With AI DevFeed: [Scaling out Distroless adoption With AI]() Original publisher: [Read original article]() Author: Jia Yee Chong Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [Grab Tech]() Topics: [Security](), [migration](), [Dockerfile](), [Vulnerabilities](), [make](), [ci](), [configuration](), [Docker](), [Docker Image](), [Testcontainers](), [MySQL]() Tags: [artificial-intelligence](), [ci](), [containers](), [devsecops](), [docker](), [docker-image](), [engineering](), [migration](), [mysql](), [security](), [testcontainers](), [testing](), [vulnerabilities]() ### AI overview Grab describes migrating services from heavy base images to Distroless images to reduce security risks and eliminate unnecessary binaries and associated CVEs. The article explains the runtime-failure risks of this migration and presents medium tests using Docker images, Testcontainers, and network proxies to verify configuration and runtime dependencies in CI. ### Source excerpt Distroless adoption at Grab Grab is migrating from heavy base images to Distroless images to reduce security risks. By limiting each container to the application and its runtime dependencies, we shed non-essential binaries and associated Common Vulnerabilities and Exposures (CVEs). This migration is more than a compliance mandate; it is a strategic security decision to build a more resilient environment. Why Distroless requires rigorous testing Distroless adoption risk: Runtime failure Shifting to Distroless images introduces a critical technical risk: Runtime Failure. A service might build perfectly in Continuous Integration (CI), but fail at the deployment stage due to: Missing shared objects: Binaries might require specific libraries (.so files) present in Ubuntu but absent in Distroless. Implicit links: Third-party tools might expect specific system utilities or directory structures. Testing is required to ensure two things: The service spins up with the correct configuration. All runtime dependencies remain intact. Scaling this verification across thousands of services manually? That would take years, unless we found a way to automate the trust. The testing methodology As we perform changes to the Dockerfile definition of our services, it is important for us to include the corresponding test strategy to ensure that the changes that we make do not introduce a regression to our running services. Assessing the change introduced to our services, the lowest possible testing boundary would be that of what we define as medium tests in Grab. Medium tests in Grab At Grab, we categorize our test suites into 3 main sizes: small, medium and large. Small tests refer to functional tests whereby mocks are introduced via dependency injection. Large tests refer to end-to-end tests that run on actual services in our staging environment where nothing is mocked. Figure 1: Architecture diagram of a medium test environment Medium tests sit between the small and large tests. External ## Running MongoDB in Docker - A Complete Guide with Examples DevFeed: [Running MongoDB in Docker - A Complete Guide with Examples]() Original publisher: [Read original article]() Author: Nic Raboy Published: 2026-05-29T12:00:00Z Content type: tutorial Language: en Sources: [Nic Raboy]() Topics: [MongoDB](), [Docker](), [Docker Compose](), [Docker Container](), [Deployment](), [Docker Image](), [Authentication](), [Command-line interface]() Tags: [authentication](), [command-line](), [deployment](), [docker](), [docker-container](), [docker-image](), [examples](), [guide](), [linux](), [macos](), [mongodb](), [rancher](), [tutorial](), [windows]() ### AI overview A practical tutorial on deploying MongoDB with Docker for local or self-hosted use. It covers prerequisites, downloading official MongoDB Community Edition images, running MongoDB in an isolated container, port mapping, authentication configuration, and safer handling of sensitive information. ### Source excerpt So you're looking to self-host MongoDB or start dabbling with it in a local setting? There are a few options to get started if you don't want to jump directly into MongoDB Atlas, one of those options ... The post Running MongoDB in Docker - A Complete Guide with Examples appeared first on DataCamp. ## Android Security: mobsfscan DevFeed: [Android Security: mobsfscan]() Original publisher: [Read original article]() Author: Matthew Dolan Published: 2026-01-16T17:51:35Z Content type: tutorial Language: en Sources: [Stories by Matthew Dolan on Medium]() Topics: [Android Security](), [Mobile Security](), [Security](), [GitHub Actions](), [CI/CD](), [GitHub](), [Docker Image]() Tags: [android-app-development](), [android-security](), [androiddev](), [build-secure-apps](), [ci-cd](), [docker-image](), [github](), [github-actions](), [mobile-security](), [security]() ### AI overview A tutorial on using the free, open-source mobsfscan tool to detect insecure code patterns in mobile applications. It focuses on running mobsfscan with GitHub Actions and uploading SARIF results to GitHub's Security tab. ### Source excerpt Not a medium member? "Read for free" Continue reading on Stackademic " ## Secure and Free MinIO Chainguard Containers DevFeed: [Secure and Free MinIO Chainguard Containers]() Original publisher: [Read original article]() Published: 2025-10-27T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Containers](), [Docker Image](), [Security](), [vulnerability](), [Amazon S3](), [Open Source](), [CI/CD]() Tags: [chainguard-containers](), [ci-cd](), [container](), [containers](), [docker-image](), [minio](), [minio-containers](), [minio-docker-containers](), [object-storage](), [open-source](), [s3](), [security](), [vulnerability](), [zero-cve-minio-containers]() ### AI overview The article explains that MinIO stopped publishing free community container images and describes the resulting maintenance and security concerns for developers. It presents Chainguard's free MinIO and MinIO Client container images as an alternative. ### Source excerpt MinIO pulled its free images--but Chainguard has you covered. Get zero-CVE, continuously built MinIO and MinIO Client containers, free and secure from Chainguard. ## Gradle Now Maintains the Official Docker Image DevFeed: [Gradle Now Maintains the Official Docker Image]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2025-09-15T04:00:00Z Content type: release Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Docker Image](), [Docker](), [Docker Hub](), [CI/CD](), [GitHub Actions](), [GitLab](), [Jenkins]() Tags: [ci-cd](), [docker](), [docker-hub](), [docker-image](), [github](), [github-actions](), [gitlab](), [gradle](), [jenkins](), [open-source](), [releases](), [support]() ### AI overview Gradle is now the official maintainer of the Gradle Docker image on Docker Hub. The article explains that the image will be kept current with Gradle releases, including security updates, while its usage, CI workflows, and community support continue to evolve. ### Source excerpt We're excited to announce we're now the official maintainer of the Gradle image on Docker Hub. For years, developers have relied on the Gradle Docker image to run builds in containers and CI/CD pipelines. Originally created and maintained by community contributor Keegan Witt, this image became a trusted resource for thousands of teams. Today, we're bringing it under the Gradle organization to ensure it remains reliable, up to date, and aligned with Gradle's release cadence. Why this Matters Docker is a critical part of modern software delivery. Many teams build and test their projects in containerized environments, and CI/CD platforms like GitHub Actions, GitLab CI, and Jenkins depend on official images to provide consistency and trust. By becoming the official maintainer of the Gradle Docker image, we can: Provide timely updates for each Gradle release, including security fixes Ensure alignment with the official Gradle -bin distributions Collaborate with the community to evolve the image for new use cases Provide support through the standard support channels (Slack and Community Forum) This also reduces the burden on individual contributors who've generously kept the image running until now. A big Thank You We want to recognize Keegan Witt, who has maintained the Gradle Docker image for years. His diligent work ensured developers could trust the image long before it became officially supported. We're grateful for his contributions and stewardship! What to Expect Going Forward The official Gradle Docker image will continue to be published under hub.docker.com/_/gradle. Images will be kept aligned with Gradle releases to the greatest extent possible. We'll review and evolve best practices for image usage, including improvements for CI workflows and ephemeral build environments. Using the Image Try the latest official image today: docker pull gradle:latest Or specify a versioned tag: docker pull gradle:9.0.0-jdk17 Get Involved The Gradle Docker image remains open sour ## Docker Build and Run Platforms and Resolving exec /usr/bin/sh: exec format error DevFeed: [Docker Build and Run Platforms and Resolving exec /usr/bin/sh: exec format error]() Original publisher: [Read original article]() Author: Hiks Gerganov Published: 2025-09-06T06:29:25Z Content type: tutorial Language: en Sources: [Baeldung - Ops]() Topics: [Docker](), [Dockerfile](), [Docker Container](), [Docker Image](), [Containers](), [Debian](), [Bash](), [cURL]() Tags: [bash](), [configuration](), [curl](), [debian](), [docker](), [docker-container](), [docker-errors](), [errors](), [image](), [platforms]() ### AI overview This tutorial explains how Docker build and run platforms affect container compatibility. It demonstrates building and running a Docker image with a Dockerfile, specifying target platforms, and diagnosing exec format errors caused by mismatched architectures or other execution issues. ### Source excerpt Explore Docker build and run platforms, along with errors that they might lead to. Further, learn about alternative reasons for exec format error issues. Related Stories Troubleshooting the no configuration file provided: not found Error in Docker Compose What Is the Runtime Performance Cost of a Docker Container? Using a Package Manager in GitHub Actions ## Benchmarking Docker image registries DevFeed: [Benchmarking Docker image registries]() Original publisher: [Read original article]() Author: Tom Published: 2025-08-31T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [docker registry](), [benchmarking](), [Command-line interface](), [Docker Image]() Tags: [bash](), [benchmark-docker-pull](), [benchmarking](), [compare-docker-registries](), [devops](), [devops-benchmarking-tools](), [docker](), [docker-cli-tips](), [docker-hub](), [docker-image-pull-speed](), [docker-performance-testing](), [docker-registry](), [docker-registry-benchmark](), [go](), [harbor](), [harbor-vs-artifactory](), [how-to](), [hyperfine-examples](), [hyperfine-tutorial](), [linux](), [performance](), [registries]() ### AI overview A practical guide to benchmarking Docker image registries with the Hyperfine CLI tool. It compares image pull performance between registries such as Artifactory and Harbor, while noting that the informal results primarily reflect network speed. ### Source excerpt Learn how to benchmark Docker registry performance using the Hyperfine CLI tool. A simple way to compare image pull speeds between registries like Artifactory, Harbor, Docker Hub, and Quay. ## 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. ## Optimizing Docker Image Builds for Size and Build Time DevFeed: [Optimizing Docker Image Builds for Size and Build Time]() Original publisher: [Read original article]() Author: Pranshu Raj Published: 2025-07-31T17:25:43Z Content type: tutorial Language: en Sources: [Pranshu Raj - blog on backend systems, performance and sidequests]() Topics: [Docker](), [Docker Image](), [Dockerfile](), [build performance](), [build times](), [Benchmark](), [Go Language]() Tags: [alpine](), [benchmark](), [build-performance](), [build-times](), [docker](), [docker-image](), [docker-image-size](), [go](), [how-to]() ### AI overview This tutorial describes optimizing a Go backend Docker image using Alpine base images and multi-stage builds. The reported changes reduced image size from 1.29 GB to 27.1 MB and build time from 43.8 seconds to 23.6 seconds. ### Source excerpt How to optimize (and benchmark) docker image builds for build time and image size. ## Teaching Python with Codespaces DevFeed: [Teaching Python with Codespaces]() Original publisher: [Read original article]() Author: Pamela Fox (noreply@blogger.com) Published: 2025-06-01T15:14:00Z Content type: tutorial Language: en Sources: [Pamela Fox]() Topics: [Python](), [GitHub](), [Development](), [configuration](), [vs-code](), [Docker](), [Docker Image](), [Dockerfile]() Tags: [configuration](), [docker](), [github](), [python](), [tutorials](), [vs-code](), [vscode]() ### AI overview A tutorial on using GitHub Codespaces to teach Python, including browser-based VS Code environments and dev container configurations. It covers simple devcontainer.json files, Python-specific images, custom Dockerfiles, and Docker-based project setup for web app, data science, and generative AI classes. ### Source excerpt Whenever I am teaching Python workshops, tutorials, or classes, I love to use GitHub Codespaces. Any repository on GitHub can be opened inside a GitHub Codespace, which gives the student a full Python environment and a browser-based VS Code. Students spend less time setting up their environment and more time actually coding - the fun part! In this post, I'll walk through my tips for using Codespaces for teaching Python, particularly for classes about web apps, data science, or generative AI. Getting started You can start a GitHub Codespace from any repository. Navigate to the front page of the repository, then select "Code" > "Codespaces" > "Create codespace on main": By default, the Codespace will build an environment based off a universal Docker image, which includes Python, NodeJS, Java, and other popular languages. But what if you want more control over the environment? Dev Containers A dev container is an open specification for describing how a project should be opened in a development environment, and is supported by several IDEs, including GitHub Codespaces and VS Code (via Dev Containers extension). To define a dev container for your repository, add a devcontainer.json that describes the desired Docker image, VS Code extensions, and project settings. Let's look at a few examples, from simple to complex. A simple dev container configuration The simplest devcontainer.json specifies a Docker image, like from Docker Hub or the Microsoft Artifact Registry. Microsoft provides several Python-specific images optimized for dev containers. For example, my python-3.13-playground repository sets up Python 3.13 using one of those images, and also configures a few settings and default extensions: { "name": "Python 3.13 playground", "image": "mcr.microsoft.com/devcontainers/python:3.13-bullseye", "customizations": { "vscode": { "settings": { "python.defaultInterpreterPath": "/usr/local/bin/python", "python.linting.enabled": true }, "extensions": [ "ms-python.python", "ms-p ## Using GoReleaser and GitHub Actions to release Rust and Zig projects DevFeed: [Using GoReleaser and GitHub Actions to release Rust and Zig projects]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2025-01-02T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Rust](), [Zig](), [GitHub Actions](), [Cross-Compilation](), [releases](), [configuration](), [Docker Image]() Tags: [changelog](), [cross-compilation](), [docker](), [github-actions](), [release](), [rust](), [zig]() ### AI overview A tutorial on using GoReleaser v2.5 with GitHub Actions to build, package, sign, and publish Rust and Zig projects across multiple platforms. It covers configuration, cross-compilation, changelog generation, Docker images, and release automation. ### Source excerpt GoReleaser v2.5 is out with Rust and Zig support - let's explore how we can use it! ## 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. ## Run and Auto-Update Docker Containers on NixOS DevFeed: [Run and Auto-Update Docker Containers on NixOS]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2024-11-21T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [Home Assistant](), [Docker Image](), [podman](), [Raspberry Pi](), [systemd](), [Containers]() Tags: [automatically](), [docker](), [docker-image](), [home-assistant](), [how-to](), [pi-4](), [podman](), [raspberry-pi](), [systemd](), [update]() ### AI overview A tutorial showing how to run Home Assistant in a Docker or Podman container on NixOS, including configuration for host networking and a Zigbee USB dongle. It also explains how to automate image updates and prune old images with systemd timers. ### Source excerpt Learn how to run the Home Assistant Docker image on NixOS on a Raspberry Pi 4 or other NixOS machines and how to keep it up to date automatically. ## How to Use the Materialize Emulator DevFeed: [How to Use the Materialize Emulator]() Original publisher: [Read original article]() Published: 2024-10-15T22:00:00Z Content type: tutorial Language: en Sources: [Dennis Felsing]() Topics: [Emulator](), [Docker Image](), [Testing]() Tags: [docker-image](), [emulator](), [how-to](), [qa](), [testing]() ### AI overview This article introduces the Materialize Emulator, a Docker image used during testing to maintain a locally hosted version of Materialize. It directs readers to the Materialize blog for the full post. ### Source excerpt In our last blog about our Quality Assurance (QA) team, we gave an overview of the QA process, including our software and testing methods. One of our key tools during testing is the Materialize Emulator, a Docker image that allows you to maintain a locally hosted version of Materialize. Read the rest of the blog post over on the Materialize blog. ## Deploying applications to Fly.io without Docker DevFeed: [Deploying applications to Fly.io without Docker]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2024-10-05T06:30:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [fly.io](), [fly](), [Skopeo](), [Docker Image](), [docker registry](), [Nix](), [Command-line interface](), [Deployment]() Tags: [cli](), [deployment](), [docker](), [docker-image](), [docker-registry](), [fly](), [fly-io](), [nix](), [oci-registry](), [skopeo]() ### AI overview A guide to deploying applications on Fly.io without installing Docker locally. It explains how to use Nix to build an OCI image and Skopeo to copy the image archive to Fly.io's registry before deployment. ### Source excerpt A quick guide to deploying apps to Fly.io without a local Docker installation ## My first 3 months at incident.io DevFeed: [My first 3 months at incident.io]() Original publisher: [Read original article]() Author: Lambert Le Manh Published: 2024-08-02T15:14:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [data](), [BigQuery](), [Docker](), [Cloud](), [Docker Image](), [ci](), [PostgreSQL](), [cloud-infrastructure](), [Docker Compose]() Tags: [bigquery](), [ci](), [cloud](), [cost](), [data](), [development](), [docker](), [docker-image](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [json](), [outage](), [platform](), [post-mortem](), [postgresql](), [registry](), [slack-incident](), [storage](), [tools]() ### AI overview A Data Engineer reviews their first three months at incident.io, focusing on scaling the development platform, evaluating alternatives to Fivetran for PostgreSQL data ingestion, and reducing platform costs. The work included storing dbt artifacts in Google Cloud Storage and using custom Docker images in CircleCI and production workflows. ### Source excerpt A review of my first three months as Data Engineer on the Data team working on improving the development platform, experimenting with different data ingestion tools, and cutting down on overall platform costs. ## 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. ## Best practices for patching and deprecating Docker images DevFeed: [Best practices for patching and deprecating Docker images]() Original publisher: [Read original article]() Author: Tom Published: 2024-02-09T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [Docker Image](), [Security](), [DevOps]() Tags: [best-practices](), [devops](), [devops-docker-management](), [docker](), [docker-image](), [docker-image-deprecation](), [docker-image-maintenance](), [docker-image-patching](), [docker-security-best-practices](), [docker-update-strategies](), [how-to](), [immutability](), [linux](), [security]() ### AI overview This article presents practices for maintaining Docker images securely and predictably. It recommends deprecating images before deleting them, notifying users of upcoming breaking changes, upgrading base images quarterly, and pinning versions to keep rebuilds stable. ### Source excerpt Learn the best practices for patching and deprecating Docker images to maintain security and stability in your DevOps workflows. ## Checking compressed size of Docker image DevFeed: [Checking compressed size of Docker image]() Original publisher: [Read original article]() Author: Tom Published: 2024-01-24T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker Image](), [Docker](), [Containers](), [Bash](), [Jenkins]() Tags: [bash](), [bash-function-for-docker](), [compressed-docker-image](), [containers](), [docker](), [docker-image](), [docker-image-metrics](), [docker-image-size](), [docker-optimization](), [docker-performance](), [how-to](), [linux](), [measurements]() ### AI overview The article explains how to use Docker image compressed size as a development metric for estimating download-time impact, while comparing it with uncompressed size to approximate extraction and startup-time impact. It presents a Bash function to simplify the measurements. ### Source excerpt Learn how to check the compressed size of Docker images to optimize download and startup times, using a simple bash function for accurate measurements. ## Trifecta Technology DevFeed: [Trifecta Technology]() Original publisher: [Read original article]() Published: 2024-01-18T09:22:53Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [Open Source](), [Software](), [C++](), [SQLite](), [JavaScript](), [Docker Image]() Tags: [c-plus-plus](), [database](), [docker-image](), [javascript](), [open-source](), [programming](), [technology]() ### AI overview An article explaining the technology behind Trifecta, an open-source image-sharing site designed as a small, self-contained service that users can run themselves. It discusses modern C++ libraries, SQLite, JavaScript, build and distribution choices, type-safe data access, and small Docker images. ### Source excerpt Trifecta is a simple open source image sharing site, built with a combination of modern C++, database and web technologies. Intended to both be useful and make some points. This page sets out to explain the underlying technology of this small yet hopefully useful piece of software. More background can be found on its main page, where you can also read a bit about why I built this software. In short, 1: I need an image sharing site I trust and that does not track its users and 2: I want to show that you can still run a service yourself safely. ## 3 tips for rebuilding a Docker image faster (and save CI seconds!) DevFeed: [3 tips for rebuilding a Docker image faster (and save CI seconds!)]() Original publisher: [Read original article]() Author: Liran Tal Published: 2023-12-28T05:00:00Z Content type: tutorial Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Docker](), [Docker Image](), [Dockerfile](), [Containers](), [CI/CD]() Tags: [ai](), [blog](), [ci](), [ci-cd](), [containers](), [dependency](), [deployment](), [devops](), [docker](), [docker-image](), [engineering](), [image](), [python]() ### AI overview This tutorial presents three ways to rebuild Docker images faster and reduce CI time: add a .dockerignore file, use a dependency lockfile, and group commands. ### Source excerpt Learn about three great ways to rebuild a Docker image faster: Add a .dockerignore file to your repository, use a dependency lockfile, and group commands! ## 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. [Next page]()