You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13Lines changed: 13 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -2445,6 +2445,7 @@ List
2445
2445
2446
2446
<details>
2447
2447
<summary>What is Docker? What are you using it for?</summary><br><b>
2448
+
Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.
2448
2449
</b></details>
2449
2450
2450
2451
<details>
@@ -2486,10 +2487,12 @@ Docker daemon redirects output from container to Docker CLI which redirects it t
2486
2487
2487
2488
<details>
2488
2489
<summary>How do you run a container?</summary><br><b>
2490
+
docker run
2489
2491
</b></details>
2490
2492
2491
2493
<details>
2492
2494
<summary>What `docker commit` does?. When will you use it?</summary><br><b>
2495
+
Create a new image from a container’s changes
2493
2496
</b></details>
2494
2497
2495
2498
<details>
@@ -2513,20 +2516,30 @@ Docker daemon redirects output from container to Docker CLI which redirects it t
2513
2516
2514
2517
<details>
2515
2518
<summary>How do you remove old, non running, containers?</summary><br><b>
2519
+
1. To remove one or more Docker images use the docker container rm command followed by the ID of the containers you want to remove.
2520
+
2. The docker system prune command will remove all stopped containers, all dangling images, and all unused networks
2521
+
3. docker rm $(docker ps -a -q) - This command will delete all stopped containers. The command docker ps -a -q will return all existing container IDs and pass them to the rm command which will delete them. Any running containers will not be deleted.
2516
2522
</b></details>
2517
2523
2518
2524
##### Dockerfile
2519
2525
2520
2526
<details>
2521
2527
<summary>What is Dockerfile</summary><br><b>
2528
+
Docker can build images automatically by reading the instructions from a Dockerfile. A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image.
2522
2529
</b></details>
2523
2530
2524
2531
<details>
2525
2532
<summary>What is the difference between ADD and COPY in Dockerfile?</summary><br><b>
2533
+
COPY takes in a src and destination. It only lets you copy in a local file or directory from your host (the machine building the Docker image) into the Docker image itself.
2534
+
ADD lets you do that too, but it also supports 2 other sources. First, you can use a URL instead of a local file / directory. Secondly, you can extract a tar file from the source directly into the destination.
2535
+
Although ADD and COPY are functionally similar, generally speaking, COPY is preferred. That’s because it’s more transparent than ADD. COPY only supports the basic copying of local files into the container, while ADD has some features (like local-only tar extraction and remote URL support) that are not immediately obvious.
2526
2536
</b></details>
2527
2537
2528
2538
<details>
2529
2539
<summary>What is the difference between CMD and RUN in Dockerfile?</summary><br><b>
2540
+
RUN lets you execute commands inside of your Docker image. These commands get executed once at build time and get written into your Docker image as a new layer.
2541
+
CMD is the command the container executes by default when you launch the built image. A Dockerfile can only have one CMD.
2542
+
You could say that CMD is a Docker run-time operation, meaning it’s not something that gets executed at build time. It happens when you run an image. A running image is called a container.
0 commit comments