Docker Config Reference (docker rename / restart / rm)

Examples of the Docker Rename Command

The docker rename command modifies the name of an existing container, allowing for improved organization without altering its state, data, or configuration. This operation can be performed on both running and stopped containers, facilitating management in dynamic environments

docker rename oldcontainer newcontainer

This command renames the container identified as "oldcontainer" to "newcontainer". It updates the container's metadata in the Docker daemon, ensuring that subsequent references, such as in logs or inspections, utilize the new name while preserving all runtime properties and network attachments.

docker rename db-old db-new

This command renames a database container from "db-old" to "db-new". It is particularly useful in development workflows where container names need to reflect updated roles or versions, maintaining continuity in service discovery without requiring recreation or data migration.

docker rename app1 app-prod

This command changes the name of the container "app1" to "app-prod". It supports environment-specific labeling, such as transitioning from testing to production, and ensures that any linked services or scripts referencing the container adapt seamlessly to the new identifier.

docker rename tempcontainer permanentcontainer

This command renames "tempcontainer" to "permanentcontainer". It aids in lifecycle management by converting temporary or experimental containers into persistent ones, without impacting their internal processes or external exposures.

docker rename worker-1 worker-primary

This command renames "worker-1" to "worker-primary". In orchestrated setups, it facilitates role adjustments, such as designating a primary worker, while keeping the container's ID and configurations intact for consistent monitoring and scaling.

Examples of the Docker Restart Command

The docker restart command halts and then restarts a container, preserving its configuration and data. This operation is equivalent to a sequential stop and start, making it suitable for applying changes or recovering from transient issues.

docker restart mycontainer

This command restarts the container "mycontainer" by first stopping its processes gracefully and then initiating them anew. It is effective for refreshing application states, such as reloading configurations, without the need for manual intervention or data loss.

docker restart --time 30 dbcontainer

This command restarts "dbcontainer" with a 30-second grace period specified by the --time flag, allowing processes to shut down cleanly before forcible termination. It minimizes disruption in database operations, ensuring transactional integrity during maintenance.

docker restart webapp

This command restarts the "webapp" container, which can resolve issues like memory leaks or stalled connections in web services. It maintains mounted volumes and network bindings, enabling quick recovery in production scenarios.

docker restart workercontainer

This command restarts "workercontainer", suitable for task-based workers in queues or batch processing. It preserves the container's environment variables and entrypoint, allowing seamless continuation of interrupted tasks.

docker restart --time 10 appcontainer

This command restarts "appcontainer" with a 10-second timeout, balancing rapid recovery with safe shutdown. It is useful in high-availability setups where brief downtimes are acceptable for applying updates or clearing temporary states.

Examples of the Docker Rm Command

The docker rm command removes one or more stopped containers, freeing associated resources such as storage and network allocations. It cannot remove running containers unless forced, promoting safe cleanup practices.

docker rm mycontainer

This command removes the stopped container "mycontainer", deleting its filesystem layers and metadata. It is essential for post-execution cleanup, reclaiming disk space in resource-constrained environments.

docker rm -f runningcontainer

Using the -f or --force flag, this command removes "runningcontainer" even if active, by first stopping it forcibly. It is applied in urgent scenarios, such as terminating unresponsive processes, though it risks data corruption if not used cautiously.

docker rm -v dbcontainer

This command removes "dbcontainer" and its associated anonymous volumes with the -v or --volumes flag. It ensures complete data erasure, preventing orphaned volumes from consuming storage, which is critical for secure database decommissioning.

docker rm container1 container2

This command removes multiple stopped containers, "container1" and "container2", in a single operation. It streamlines batch cleanup, enhancing efficiency in testing pipelines or after bulk deployments.

docker rm -f -v appcontainer

Combining -f for force and -v for volumes, this command removes "appcontainer" regardless of state and deletes linked volumes. It provides thorough resource reclamation, suitable for automated scripts in continuous integration environments where complete resets are required.