You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ docker-compose -f docker-compose.yml up -d
Creating network "docker-compose_backend" with driver "bridge"
Creating docker-compose_host.docker.internal_1 ... done
Creating docker-compose_tcp_message_emitter_1 ... done
# i have more networks but I only show the relevant one
$ docker network ls
NETWORK ID NAME DRIVER SCOPE
a5aa8ca04a22 docker-compose_backend bridge local
$ sudo docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' docker-compose_host.docker.internal_1
172.28.0.2
$ sudo ufw allow from 172.28.0.2 proto tcp to any port 2323
Rules updated
All of the following nc commands on the host give no output:
I recently updated the examples, I replaced the container name docker-host with host.docker.internal maybe that is causing problems. Will have a deeper look into it this weekend.
@qoomon Thanks it works now. It seems like dashes are not supported in service/container names. Do you know why? because I havent found that this restriction is mentioned in the docker compose docs
This is similar to #21
I followed the README but I still dont get any visible output on the terminal which listens with
nc
.All of the following
nc
commands on the host give no output:Unfortunately I didnt find the problem myself so far, maybe you have some ideas.
The text was updated successfully, but these errors were encountered: