Skip to content

Commit cbda545

Browse files
author
Arie Bregman
authored
Merge pull request bregman-arie#56 from apuzyrevsky/patch-1
Update README.md
2 parents fd7e129 + 72f1f58 commit cbda545

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
@@ -2463,6 +2463,7 @@ List
24632463

24642464
<details>
24652465
<summary>What is Docker? What are you using it for?</summary><br><b>
2466+
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.
24662467
</b></details>
24672468

24682469
<details>
@@ -2504,10 +2505,12 @@ Docker daemon redirects output from container to Docker CLI which redirects it t
25042505

25052506
<details>
25062507
<summary>How do you run a container?</summary><br><b>
2508+
docker run
25072509
</b></details>
25082510

25092511
<details>
25102512
<summary>What `docker commit` does?. When will you use it?</summary><br><b>
2513+
Create a new image from a container’s changes
25112514
</b></details>
25122515

25132516
<details>
@@ -2531,20 +2534,30 @@ Docker daemon redirects output from container to Docker CLI which redirects it t
25312534

25322535
<details>
25332536
<summary>How do you remove old, non running, containers?</summary><br><b>
2537+
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.
2538+
2. The docker system prune command will remove all stopped containers, all dangling images, and all unused networks
2539+
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.
25342540
</b></details>
25352541

25362542
##### Dockerfile
25372543

25382544
<details>
25392545
<summary>What is Dockerfile</summary><br><b>
2546+
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.
25402547
</b></details>
25412548

25422549
<details>
25432550
<summary>What is the difference between ADD and COPY in Dockerfile?</summary><br><b>
2551+
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.
2552+
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.
2553+
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.
25442554
</b></details>
25452555

25462556
<details>
25472557
<summary>What is the difference between CMD and RUN in Dockerfile?</summary><br><b>
2558+
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.
2559+
CMD is the command the container executes by default when you launch the built image. A Dockerfile can only have one CMD.
2560+
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.
25482561
</b></details>
25492562

25502563
<details>

0 commit comments

Comments
 (0)