According to your screen dump you have your port 80 mapped to the Traefik container
58cd5b59579c traefik:v2.2 "/entrypoint.sh --lo…" 16 minutes ago Up 15 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp frappe_docker_traefik_1
The listen address of this mapping is 0.0.0.0 on both port 80 HTTP, and 443 ...
The "official" nginx image has a specific path where it looks for files. You can either copy a file into the image by creating a new image from it or mount your files into this path as a volume.
To copy files, have a folder with your index.html and a Dockerfile that looks like this:
COPY index.html /usr/share/nginx/html
Then build a new ...
The docker build command builds Docker images from a Dockerfile and a “context”. A build’s context is the set of files located in the specified PATH or URL. The build process can refer to any of the files in the context. For example, your build can use a COPY instruction to reference a file in the context.
From docker build documentation.
As you run the ...
Did you only try to reach localhost? Or even 0.0.0.0 or 127.0.0.1?
Depending on the operating system, docker config and the internal networking setup, some problem can occurs to reach the docker network.
You can inspect the container to get the network IP, maybe you can go there https://stackoverflow.com/a/20686101/2904965
This at least builds and runs:
root@mordor:/home/nicholas/docker/nginx# ls -al
drwxrwxr-x 2 nicholas nicholas 4096 Nov 13 17:18 .
drwxrwxr-x 3 nicholas nicholas 4096 Nov 13 16:12 ..
-rw-rw-r-- 1 nicholas nicholas 49 Nov 13 17:18 dockerfile
-rw-rw-r-- 1 nicholas nicholas 56 Nov 13 17:18 index.html
Scaling is increasing the number of containers for any specific service. This is primarily helpful for a cluster, not on a single host setup like yours. When you scale your application up in a cluster, multiple containers of the same service get spread across the cluster (Based on their availability (Resource or anyway)). This makes the distribution of load ...