Details
-
Suggestion
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
21
-
c9e6cdc19 (dev), d5d9317c3 (dev), 60ff03736 (dev), 28bff27b8 (dev), b85acc835 (dev), 791455c03 (dev), e88a2ed83 (dev), f698255df (dev), 8427f997f (dev), 0a5641e72 (dev), 9fc4f26c8 (dev), 956795bda (dev), cb8e5e0dd (dev), 68ceb847d (dev)
-
Foundation Sprint 101, Foundations Sprint 102, Foundation Sprint 103, Foundation Sprint 104, Foundation Sprint 105, Foundation Sprint 106, Foundation Sprint 107, Foundation Sprint 108
Description
Dockers REST api by default listens on a unix socket ( on mac / linux ) or a named pipe ( on windows ).
To allow Qt Creator ( and others ) to interface with this API we need a way to either directly support some form of url ( e.g. unix:///var/run/docker.socket ), or specify an alternative ( in this case QLocalSocket ) socket for QNAM to use for certain requests.
Trying to implement this currently is not feasible without re-implementing / copying the private HTTP Request classes. Using the QNetworkBackend mechanism is also not an option as it is private, and not used by the HTTP Request classes that QNAM uses.
As an example, see here for how the curl api supports this: https://github.com/cqbqdd11519/DockerClient/blob/master/docker.cpp#L238