惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
有赞技术团队
有赞技术团队
H
Help Net Security
V
Visual Studio Blog
F
Fortinet All Blogs
Apple Machine Learning Research
Apple Machine Learning Research
博客园 - 司徒正美
G
Google Developers Blog
Google DeepMind News
Google DeepMind News
腾讯CDC
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Stack Overflow Blog
Stack Overflow Blog
I
InfoQ
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
L
LangChain Blog
N
Netflix TechBlog - Medium
罗磊的独立博客
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG
Hugging Face - Blog
Hugging Face - Blog
A
About on SuperTechFans
aimingoo的专栏
aimingoo的专栏
Recent Announcements
Recent Announcements

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Docker – ARG Directive, .dockerignore, and Docker Volumes
Ramya Perumal · 2026-06-28 · via DEV Community

ARG Directive

The ARG directive acts like a variable. We can define it inside the Dockerfile and change its value during the image build process.

ARG PYTHON_VERSION=3.8
FROM python:${PYTHON_VERSION}-slim

Here, the Python version in the Dockerfile is set to 3.8. However, during the build process, we can change it to 3.10.

docker build -f Dockerfile --build-arg PYTHON_VERSION=3.10 -t helloworld_flask:v1 .

  • -t means tag.
  • -f means Dockerfile path.

We can use ARG to make base image versions and other build-time values configurable.

Example

FROM node:20-alpine

# 1. Define the arguments
ARG APP_DIR=app
ARG INSTALL_ARGS="--omit=dev"

# 2. Use them in instructions
WORKDIR /${APP_DIR}
COPY . .
RUN npm install ${INSTALL_ARGS}

Note: ARG values can only be changed during the image build process. They cannot be changed during container creation.


Docker Ignore

A .dockerignore file is used to specify files and directories that should not be copied into the Docker build context.

Create a file named .dockerignore in the application's root directory.

Examples of files and folders that can be ignored:

Dockerfile
.venv
__pycache__
*.pyc
requirements.txt
.git
.gitignore

Ignoring unnecessary files reduces the build context size and speeds up image builds.


Docker Volumes

Generally, when a container is created, a writable layer is also created.

If we create files inside the container, they are stored in the writable layer. However, when the container is deleted, all data in the writable layer is lost.

What if we need to store files permanently on the host machine?

This is where Docker volumes come into the picture.

Docker volumes allow data to persist independently of the container lifecycle.

When a volume is mounted between a host directory and a container directory:

  • Files created in the container appear on the host machine.
  • Files created on the host machine appear inside the container.
  • Changes are synchronized between both locations.

Types of Docker Volumes

  1. Bind-Mounted Volumes
  2. Docker Managed Volumes (Named Volumes)

1. Bind-Mounted Volumes

A bind mount creates a mapping between a host directory and a container directory.

docker run -it -v ./data:/data busybox:1.36 sh

Here:

  • ./data = Host machine directory
  • /data = Container directory

Characteristics:

  • Tightly coupled with the host file system.
  • Multiple containers can share the same host directory.
  • Changes made in either location are reflected in the other.

Note: The host directory is not deleted when the container is removed.


2. Docker Managed Volumes (Named Volumes)

Create a Docker-managed volume:

docker volume create dockersession

This creates a volume outside the container lifecycle.

List Volumes

docker volume ls

Inspect a Volume

docker volume inspect dockersession

This displays information about the volume, including its mount location.

Example Linux location:

/var/lib/docker/volumes/dockersession/_data

Mount the Volume to a Container

docker run -it -v dockersession:/data123 busybox:1.36 sh

Here:

  • dockersession = Volume name
  • /data123 = Container directory

Multiple containers can use the same volume for data sharing.

Find Containers Using a Specific Volume

docker ps -a --filter volume=dockersession

One of the major benefits of Docker volumes is that they are completely decoupled from the container lifecycle.

When a container is deleted, the volume and all its data remain safely stored on the host machine.


Interview Questions

Question:

What is the primary use of the ARG instruction in Docker?

Answer: To pass build-time variables to the Dockerfile.


Question:

Which of the following is true about ARG variables in Docker?

Answer: They are used only during the image build process.


Question:

Can an ARG variable be used in a RUN instruction within a Dockerfile?

Answer: Yes, but only after it has been declared.


Question:

Which files can be ignored using .dockerignore?

Answer: Any file or directory within the build context.


Question:

What is the purpose of Docker volumes?

Answer: To store data that persists even after a container is destroyed.


Question:

What is the default location of Docker volumes on Linux systems?

Answer:

/var/lib/docker/volumes


Question:

Which command allows you to list all Docker volumes?

Answer:

docker volume ls


Question:

In which scenario would you use a bind-mounted volume?

Answer: When you need to share specific directories between the host machine and a container.