Skip to content

Commit 72f1f58

Browse files
authored
Update README.md
Added several answers for Docker questions.
1 parent 7086fda commit 72f1f58

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

README.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2445,6 +2445,7 @@ List
24452445

24462446
<details>
24472447
<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.
24482449
</b></details>
24492450

24502451
<details>
@@ -2486,10 +2487,12 @@ Docker daemon redirects output from container to Docker CLI which redirects it t
24862487

24872488
<details>
24882489
<summary>How do you run a container?</summary><br><b>
2490+
docker run
24892491
</b></details>
24902492

24912493
<details>
24922494
<summary>What `docker commit` does?. When will you use it?</summary><br><b>
2495+
Create a new image from a container’s changes
24932496
</b></details>
24942497

24952498
<details>
@@ -2513,20 +2516,30 @@ Docker daemon redirects output from container to Docker CLI which redirects it t
25132516

25142517
<details>
25152518
<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.
25162522
</b></details>
25172523

25182524
##### Dockerfile
25192525

25202526
<details>
25212527
<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.
25222529
</b></details>
25232530

25242531
<details>
25252532
<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.
25262536
</b></details>
25272537

25282538
<details>
25292539
<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.
25302543
</b></details>
25312544

25322545
<details>

0 commit comments

Comments
 (0)