chore: change the hostname of mongodb #24
Conversation
podman is not able to reach mongo host Change-Id: Ie4d8070ed5e1edb1ac9520ad8e4d6e9760338ee2 Signed-off-by: Florent Benoit <[email protected]>
|
It looks like Docker is able to find both hostnames, |
|
podman enables a 'dns' for the user created networks and then use the container name |
benoitf
changed the title
If we use the same name for the container and the hostname then it should work with podman correct? |
|
yes |
|
@hguerrero do you want that I change something in my pull request ? |
|
No, thanks, @benoitf I'm checking that we must change the remaining containers to have the same behavior to work with podman. I will merge this and continue working on the remaining containers. |
|
FYI the bug in podman is containers/podman#17370 |
|
@hguerrero when is planned a 0.2.2 release ? |
Description
podman is not able to reach mongo host
But as mongodb container is started with the name
microcks-mongodb, reuse the container name as hostname so other containers on the same network can also reach itPlease check on your side on Docker
Related issue(s)