You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a mysql server container running downstream of NPM. I'm forwarding port 3306 on udp/tcp from NPM -> mysql:3306.
It seems like sometimes if I restart the mysql container, the stream stops working. Sort of like the ip address or something underneath changes and NPM doesn't notice it. I think if I restart NPM the issue goes away afterwards.
Is this expected behavior? .. I don't think the same thing happens with regular proxy hosts.
To work-around, I've hardcoded an ipv4 address for my mysql container, and that seems to keep it consistent so that the stream doesn't stop working when mysql restarts.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a mysql server container running downstream of NPM. I'm forwarding port 3306 on udp/tcp from NPM -> mysql:3306.
It seems like sometimes if I restart the mysql container, the stream stops working. Sort of like the ip address or something underneath changes and NPM doesn't notice it. I think if I restart NPM the issue goes away afterwards.
Is this expected behavior? .. I don't think the same thing happens with regular proxy hosts.
To work-around, I've hardcoded an ipv4 address for my mysql container, and that seems to keep it consistent so that the stream doesn't stop working when mysql restarts.
Beta Was this translation helpful? Give feedback.
All reactions