I can't figure out how to solve this issue. I've also tried to launch both containers using -network my-network after creating my-network with docker network create my-network but it doesn't work.
I've tried using and but it doesn't work. Podman, like the docker CLI needs a linux VM to work with if run on a mac. installing it on MacOS is the predictable. How can I solve this issue? How can I let the app container connect to the database (and keep accessing also to the DB from the main host using 127.0.0.1:3306)? That said, there’s also a complete alternative to Docker CLI called Podman. You need to restart Docker Desktop after making any changes to the keychain or to the /.docker/certs.d directory in order for the changes to take effect. I can still access the database via 127.0.0.1:3306 from the main host, but I cannot access it from the app container. When the Docker Desktop application starts, it copies the /.docker/certs.d folder on your Mac to the /etc/docker/certs.d directory on Moby (the Docker Desktop xhyve virtual machine). The host networking driver only works on Linux hosts, and is not supported on Docker for Mac, Docker for Windows, or Docker EE for Windows Server. Install qemu with brew under x86 in M1 Mac OS. However -network host does not work on Mac and Windows: I just setup a x86-64 environment on arm64 M1 Mac Mini with the Ubuntu Docker image. Well, this certainly is possible and may seem like a good short-term plan to get the project out of the door, but it could leave you with a house of cards that could come tumbling down when the first critical security patch is needed for either software stack. I can access the DB from both the host system and the app container. Using Docker for Mac or Docker for Windows. Docker run -name my-db -p 127.0.0.1:3306:3306 my-db-imageĭocker run -name my-app -network host -it my-app-image
0 kommentar(er)
