MySQL and how it is run $ docker network create $ docker network connect mysql $ docker-compose up -d env file MYSQL_ROOT_PASSWORD=mysql_root_password I didn't do that for postgres and it works fine anyway.
I read about it in that thread everyone reads ( Can't connect to MySQL server: Connection refused) when they try to make MySQL works in a container behind Traefik2. That's because I read that the MySQL image exposes both 330 ports and that Traefik2 doesn't know what to do about that (I don't really get it since the tag redirects traffic to the 3306 port anyway but okay). Notice how I am setting up the mysql-db service manually. It has an ipv4 address and some funny domain names but that's irrelevant to the matter at hand. Here are my precious files that all run with docker-compose, each service in its own folder ( mysql, traefik2, postgres and tcp-echo-server) on a standard Debian installed in a VPS hosted in that cheese and wine country. Alas that tcp echo server works as intended and parrots things I send him and though I have rarely used postgres I also can connect to a Postgres server running in a container behind Traefik. I set up a basic tcp echo server in the vain hope to rule out any Traefik misconfiguration. The client just hangs out, Wireshark shows that nothing is going on after the syn/ack handshake and I am dead inside now.
I have been banging my head against the wall all day yesterday and I finally decided to sell all my computer and tech stuff and I plan to leave the city Friday night to go and live in a small community farm where I am told I can earn my food and lodgings by doing field works (picking up potatoes and doing pest control by hand I am told, it's an organic farm).Īnyway, before closing that chapter of my life I would like to understand why I couldn't get a MySQL client to talk to a MySQL server running in a container behind Traefik2.
0 kommentar(er)
