Docker Socket Configuration for Multi-Stack Communication

[MarineLeM]

Description

When the Docker orchestrator starts, it connects to the default socket. However, OpenAEV or OpenCTI stacks may run on a different socket. If xtmComposer isn't on the same socket, it cannot communicate with these services.

Proposed solution: Add a configurable socket name in the default.yaml file.

Environment

2. XTM Composer version: 1.0.0

[richard-julien]

Hi @MarineLeM , not sure to get how this situation is really possible.

[MarineLeM]

I'll let @Dimfacion answer this since he encountered this problem

[Dimfacion]

Hi @richard-julien,
You can have multiple context each with a different socket as you can see here :
https://docs.docker.com/engine/manage-resources/contexts/
I learned about it the hard way since I had Docker Desktop with all my OAEV stack on a different endpoint than the default one. After talking about it with @MarineLeM, we thought it would be nice to still use the default one but be able to override it if needed.