If you for example do docker-in-docker ( docker:did ) or a usual remote docker-eninge, you would connect using a tcp socket rather then a lock unix socket.
This socket is usually either given by a simple domain:port combination ( since tcp:// is the default if the socket scheme is not given ). This is also part of the docker-client configurations of DOCKER_HOST https://github.com/docker-library/docker/blob/6e7677bec19c214ef5445c0d2b96c56e42098ca1/docker-entrypoint.sh#L17
in elastic-agents though, one has to put http:// instead, which is undocumented and also not what is expected and not used by usual docker clients.
Can we fix this, on which layer this is mapped? using tcp:// does not work at all
If you for example do docker-in-docker ( docker:did ) or a usual remote docker-eninge, you would connect using a tcp socket rather then a lock unix socket.
This socket is usually either given by a simple domain:port combination ( since tcp:// is the default if the socket scheme is not given ). This is also part of the docker-client configurations of DOCKER_HOST https://github.com/docker-library/docker/blob/6e7677bec19c214ef5445c0d2b96c56e42098ca1/docker-entrypoint.sh#L17
in elastic-agents though, one has to put http:// instead, which is undocumented and also not what is expected and not used by usual docker clients.
Can we fix this, on which layer this is mapped? using tcp:// does not work at all