4b7a3b82ea4599711954f5086f2b1aa890614de0
This is done in a hacky way as currently there is no better way. Uses known implementation details about how tasks are scheduled to be able to operate on the underlying container. Signed-off-by: Brian Goff <cpuguy83@gmail.com> Upstream-commit: e5ec575b32d6979914dce576f1b8bb71f3057cea Component: engine
Description
No description provided
Languages
Go
92%
Shell
5.5%
Dockerfile
1.1%
Go-Checksums
0.9%
Makefile
0.3%
Other
0.2%