Oh and thank you for taking your time to help me out.
Are the two docker engines different, on how it works? Though the method described in the article worked on my osx environment and not in linux environment. And based on the documentation I have to put the host ip to make it work, so I’m trying to find a way to do that. And from the documentation that (Person A) wrote, I have to add additional environment variables when running the container. Using user-defined network will work, but then I have another container from (Person A) running a kafka server. The containers I’m working with was made by someone else(Person A). The reason that I’m trying to do it this way is because my containers aren’t actually from the official docker hub’s mongodb image. I’m trying to find a way to have every service exposed into a single ip, so every service can be reachable just by specifying different ports. Yes, user-defined network was one of the options that I’ve looked at. Note: service discovery is not available for the default bridge network, this is why it needed container linking - with service discovery container linking is not required anymore. This is the common solution for your scenario. Though, what’s wrong with creating a user defined docker network, attach the containers to this network, then leverage dns-bases service discovery for the communication amongst containers in this network? You just use the container-name and container-port to reach the service of another container. I doubt that any of those two approaches is the most useful solution in your scenario. Basically it allows other container to use network interface of another container - even localhost is the same network interface in both containers. The suggestion of is to join another container into the network namespace of another container. The article shared in the first post is from 9 years ago, its an outdated idea, which no one would use like that today. And I’m trying to avoid to use -net=host as well. I’d want to avoid using -link because I want a centralized ip that can access all the ports that is exposed from each containers. But, I’m trying to create a centralized ip so that all of my future containers can access and communicate with each other. I tried connecting it by using the mongodb’s ip directly that is listed in docker network inspect bridge and it works. cause the port 27017 is listed as “filtered”. So, the problem is mongodb can’t respond back to the sender. It seems that mongodb is accepting the connection but it isn’t responding back. I’ve run another ubuntu container as well within the same bridge network. Like in the article I’ve tried mapping the port towards the host’s interface ip in the docker bridge network for the mongodb and it still doesn’t work. I’ve port mapped it already for mongodb and the jupyter notebook to the host, and still doesn’t work.
I’m accessing jupyter notebook through my host.īut for some reason my jupyter notebook can’t communicate with the mongodb. Both of them are in a bridge network and its in the default bridge network. One running jupyter notebook and another running mongodb.
It instructs the host machine to listen on port and propagate all traffic to the port 8080 inside the docker container.I have 2 containers. p :8080 - parameter that defines the port mapping. v :/opt/youtrack/NNN - binding the YouTrack-specific 'NNN' directory on the host machine to the respective /opt/youtrack/NNN directory inside the container. name youtrack-server-instance - the arbitrary name for the container. For more details, see the official docker documentation. Use `Ctrl+PQ` in order to detach the terminal from container output. Note that pressing `Ctrl+C` when the terminal is attached to a container output causes the container to shut down.
it - a flag that attaches YouTrack container input and output including the startup logs to the terminal window. Docker run -it -name youtrack-server-instance \
0 kommentar(er)
