dnssearch | A subdomain enumeration tool | Security Testing library

It looks like the bind mount was the issue. I was mounting to /bin/usr, which was somehow causing the error.

in your docker compose i see you are using vpc1, if this is AWS, check your security groups, and allow from which computeror VM, you are connecting to the container from, to be able to access this.

From above error log, an old version of testcontainers was in use.

Upgrading the testcontainers dependency to the latest version 1.15.2 fixed above issue.

Issue with command in your example is that you're mapping local port 5000 to port 5000 in container (nothing listening on it).

Thy this: docker container run -d --name nginx --publish 5000:80 nginx

Here port 5000 on your host is getting mapped (bound) to port 80 in the container.

First of all, you didn't create a docker image, you created a docker container named: pg1 from the official image postgres,

Based on your docker inspect the output, I think it will work on host 172.17.0.4 and port 5432. So try below command -

I think the tutorial you are referring to is a bit outdated. You can run the tomcat docker container using a command like

Since you're mapping over Docker's networking you can't just bind to the loopback interface, but to the main one, so you need to bind to 0.0.0.0 not localhost or 127.0.0.1.

That will permit "external" connections, as your main machine and the Docker virtual machine's "localhost" are two different things.

This should be as simple as using the --host flag:

By default, the mysql image listens on port 3306.
In your docker run command you are using -p 3606:3606. This creates a DNAT rule from your host 3606 to the container on the same port - where no service is listening.

Try to start the container with this command(note that the source can be any port that is not in use on your host - in the example below I kept your initial port 3606):

Your kestrel server is listening at port 80.

You might have to update your docker run command to:

docker run -it -p 8000:80 --name wtp webtarjetasparquimetros:1.0

post which you should be able to browser to http://localhost:8000/

do try below commands to test docker ports

$ docker port test

-p is for publish and not for port -p takes an argument :

using -p option you can control the host machine port that you want to assign

Dockerfile has a command EXPOSE it does not enable or publish any port. But is a metadata command. It helps the developer know that this app will eventually use the port mentioned in the EXPOSE command.

there is one more option to publish -P with a capital P

it does not take any argument and publishes all the ports in EXPOSE command.

So if you don't want to get confused use -P instead of -p