In the above snapshot, we are able to access the default page from inside the container. Step 8: Let’s create a new container using the ‘nginx:no_expose’ image and expose the port 8080 on the host as we have already used port 80. In the above snapshot, we can see that we can access the nginx default page from the host on port 80 as well. Let’s run another container with the same image ‘nginx:expose’ but expose the port 80 this time. Step 7: So, we are unable to access the nginx default page because the port has not been exposed while running the container in step 3. Step 6: Finally, let’s try to access it from the host. In the above snapshot, we can see that we can successfully access the nginx default page running from a different container. Step 5: Let’s create another container that has curl already installed and access the nginx default page using the IP address of the nginx:expose container. Step 4: Let’s check the IP address of this container so that we can connect this from a different container.
In the above snapshot, we can see that the nginx default page is accessible. Step 3: Now, start a container using the ‘nginx:expose’ image, connect to it, and access the default page of nginx. Step 2: Let’s build Docker images using the above two Dockerfile. RUN apt-get update & apt-get install -y nginx Step 1: First thing, we need to create two Dockerfile, we will mention the ‘EXPOSE’ instruction in the first Dockerfile, and we will create the second one without the ‘EXPOSE’ instruction. We will create two nginx images with and without the ‘EXPOSE’ instruction mentioned in the Dockerfile and try to access the nginx within the container, from different containers, and from the host.
Given below is the example of Docker EXPOSE: How EXPOSE works in Docker?Īs we know, it is only used for documentation there is no special functionality included in this instruction which means if we don’t include this instruction in the Dockerfile, the image created using Dockerfile is still going to work in the same way, but yes, if Docker image is created by someone else and the container is getting created by someone else then who is going to create the container will get confused that on which port application is listening. The protocol is optional, we can specify whether the application is going to listen on TCP or UDP port, and protocol is not specified, then TCP is going to use by default. Here is the syntax for the ‘EXPOSE’ instruction in Dockerfile: Web development, programming languages, Software testing & others Start Your Free Software Development Course
0 kommentar(er)
