Exam XK0-005 topic 1 question 11 discussion

A. HOST:CONTAINER, 443 on the host and 8443 443:8443

A. -p HOST:CONTAINER. (Maps Port) B Invalid as that is syntaxed as CONTAINER:HOST C Invalid as it uses the -e option (ENV VARIABLE) which is not used D Invalid for CONTAINER:HOST among other things.

A. If you’re using docker compose the pattern is HOST:CONTAINER, i.e. 443 on the host and 8443 on the container would be 443:8443

https://www.howtoforge.com/getting-started-with-podman-manage-images-container-and-volumes/ which is mentioned by Rob74613 also indicates host:container so A is correct Manage Containers At this stage, we learned about container image management. And the next step, we will learn how to create and manage containers with Podman. To create a new container, we can use 'podman run' command as below. podman run -d -p 8000:80 --name hakase-nginx docker.io/library/nginx The command will create a new container named 'hakase-nginx' based on the nginx image and will expose the port 8000 on the host machine. Details command options: -d - keep the container running in the background and just print the container ID as a result. -p 8000:80 - port mapping for container and the host system. Port 8000 on the host machine, and port 80 on the container. --name hakase-nginx - specify the container name with 'hakase-nginx'. Now display all running containers on the system.

This is a useful article: https://docs.podman.io/en/latest/markdown/podman-run.1.html -p=[[ip:][hostPort]:]containerPort[/protocol] this would make "A" the correct answer

answer is B. The exposed port of an application can be mapped to a host port using the -p flag. For example, an httpd port 80 can be mapped to the host port 8080 using the following: $ podman run -p 8080:80 -d -i -t fedora/httpd

A should be correct

To create a new container, we can use 'podman run' command as below. podman run -d -p 8000:80 --name hakase-nginx docker.io/library/nginx The command will create a new container named 'hakase-nginx' based on the nginx image and will expose the port 8000 on the host machine. Details command options: -d - keep the container running in the background and just print the container ID as a result. -p 8000:80 - port mapping for container and the host system. Port 8000 on the host machine, and port 80 on the container. --name hakase-nginx - specify the container name with 'hakase-nginx'. Now display all running containers on the system.

<host_port>:<container_port>.

concur with rob

Answer is B Source: https://www.howtoforge.com/getting-started-with-podman-manage-images-container-and-volumes/ look at section 3: Manage Contatiners

Definitely A

I checked the documentation and first is host port and then the container port, so option A should be the right one. since you are exposing the port 443 on the host to the port 8443 on the container

B is correct -p 8443:443: This option specifies the port mapping. It maps port 8443 of the host machine to port 443 of the container.

Ans is A.

bbbbbbbbb

According to the Podman documentation, the host machine port is the first parameter in the command when used with the -p option: -p=[[ip:][hostPort]:]containerPort[/protocol] Under this construction, answer A would be correct. I know that Podman can be seamlessly aliased to Docker in Ubuntu but I am not sure if Docker uses a different construction. I also think that the fact that Podman is a daemonless application influences how it interfaces with the O/S ports and protocols.