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 been fighting with how to get full socket like functionality in a docker swarm environment. I tried all sorts of stuff... mulled over it for months... and then it hit me.
I have it successfully running as a global service (so one is on each node) and the trick, do not use a networked socket but a Unix socket .sock kinda config and point your services to use that. This will force the local instance to respond to the local service requesting info and be same as native socket.
Not sure what value I am adding by proxying it... I am asking in another thread.
I thought I would share as this was an issue for me and is an issue with all swarmed socket proxies....
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
Uh oh!
There was an error while loading. Please reload this page.
-
hiya.
I have been fighting with how to get full socket like functionality in a docker swarm environment. I tried all sorts of stuff... mulled over it for months... and then it hit me.
I have it successfully running as a global service (so one is on each node) and the trick, do not use a networked socket but a Unix socket .sock kinda config and point your services to use that. This will force the local instance to respond to the local service requesting info and be same as native socket.
Not sure what value I am adding by proxying it... I am asking in another thread.
I thought I would share as this was an issue for me and is an issue with all swarmed socket proxies....
Hope this helps someone else.
Beta Was this translation helpful? Give feedback.
All reactions