So at Giggl we do quite some stuff with Docker and i wanted to do some more specific things with the Docker Engine API.
The Problem
The Problem is that the CLI arguments passed to the docker
tool are not 1:1 the same passed to the daemon api, and for things like the seccomp you actually read files before sending the content to the Docker daemon.
It would be good if i could see what the docker
tool sends to the API, because while the Engine Api has a documentation, it is missing certain things or does not dive into detail to the degree i would need….well turns out i can do that using a little hack!