DevNet Associate DEVASC 200-901 Official Certification Guide by Adrian Iliesiu (z-lib.org)

f83e0f07db18 58 minutes ago /bin/sh -c #

(nop) MAINTAINER Cisco Champion... 0B

775349758637 3 weeks ago /bin/sh -c #

(nop) CMD ["/bin/bash"] 0B

<missing> 3 weeks ago /bin/sh -c mkdir

-p /run/systemd && echo 'do... 7B

<missing> 3 weeks ago /bin/sh -c set -

xe && echo '#!/bin/sh' > /... 745B

<missing> 3 weeks ago /bin/sh -c [ -z

"$(apt-get indextargets)" ] 987kB

<missing> 3 weeks ago /bin/sh -c #

(nop) ADD file:a48a5dc1b9dbfc632... 63.2MB

You probably noticed the missing image IDs at the
bottom of the history. The build process uses something
called intermediate layers to execute commands. These
layers are like temporary storage that gets rolled up into
the next layer when each stage is finished, and then the
intermediate layer is deleted.

When the image is built and ready to go, you can run it
by using the following command:

Click here to view code image

$ docker container run -p 80:80 -p 443:443 -d

myimage

bf0889f6b27b034427211f105e86cc1bfeae8c3b5ab279ccaf08c114e6794d94

$ docker ps

CONTAINER ID IMAGE COMMAND CREATED

STATUS PORTS NAMES

bf0889f6b27b myimage "nginx -g 7 seconds

ago Up 6 seconds 0.0.0.0:80->80/tcp,

elastic_maxwell

'daemon of..."

0.0.0.0:443->443/tcp

You can use the docker image rm command to remove
an image from storage. This command needs the
container ID or a name to select the appropriate
container.

DOCKER HUB