[DiscordArchive] oof, yea that's a problem, are your mysql client (workbench) and the server on the same host or is t
[DiscordArchive] oof, yea that's a problem, are your mysql client (workbench) and the server on the same host or is t
Archived author: McNaughtyVerse • Posted: 2022-05-01T19:26:53.415000+00:00
Original source
and they are in different docker images
Archived author: McNaughtyVerse • Posted: 2022-05-01T19:26:59.892000+00:00
Original source
the current image is mounted and I can access just fine
Archived author: SmilyContainer • Posted: 2022-05-01T19:27:06.263000+00:00
Original source
did you tell one to bind on a different port?
Archived author: McNaughtyVerse • Posted: 2022-05-01T19:27:08.033000+00:00
Original source
the 2nd image mounted, but I can't seem to access the database
Archived author: McNaughtyVerse • Posted: 2022-05-01T19:27:12.723000+00:00
Original source
yeah
Archived author: SmilyContainer • Posted: 2022-05-01T19:27:26.801000+00:00
Original source
ok gotta ask lol, so many people forget to bind to another port
Archived author: SmilyContainer • Posted: 2022-05-01T19:28:27.872000+00:00
Original source
if you say told backup mysql to bind to port 3307 instead of the default 3306, and it isn't responding to ya on 3307, i'd check every line of its container output
Archived author: McNaughtyVerse • Posted: 2022-05-01T19:28:57.809000+00:00
Original source
see, I can't really figure out how to check everything
Archived author: McNaughtyVerse • Posted: 2022-05-01T19:29:02.728000+00:00
Original source
I'm running a weird OS
Archived author: SmilyContainer • Posted: 2022-05-01T19:29:10.967000+00:00
Original source
i've shot myself in the foot similarly in this scenario for instance when using docker-compose and binding 3307:3307 but forgetting to mount the mysql.cnf file to tell myself to move to port 3307