Re:Don't expose the docker socket, even to a container
by throwaway2048 on Thursday September 24, 2015 @12:53AM
(#10269891)
there is no mention of seccomp because virtually no software can utilize it.
[ Parent
| on HN ]
Re:Don't expose the docker socket, even to a container
by kentonv on Thursday September 24, 2015 @02:01AM
(#10270083)
Sandstorm.io (disclosure: my project) applies mandatory seccomp and other attack surface reduction yet manages to run a lot of apps with only minimal modification:
https://docs.sandstorm.io/en/latest/developing/security-prac...
Admittedly, though, "only minimal modification" is probably too much modification for Docker's goals. That's fair. But I don't think that gives them a pass to pretend the problem doesn't exist.
Re:Don't expose the docker socket, even to a container
by geofft on Thursday September 24, 2015 @01:09AM
(#10269935)
As a Chrome, systemd, and Sandstorm user, I'm a little curious what you mean.