News for hackers. Stuff that matters.
Re:Docker and Canonical Partner on Commercially-Supported Do... by raesene6 on Wednesday November 30, 2016 @10:08AM (#13071316)
Depending on your use case, that may not be such a great idea. Unless Red Hat have back-ported it, 1.10 misses several important security advances that have come into Docker in recent versions...
Re:Docker and Canonical Partner on Commercially-Supported Do... by SEJeff on Wednesday November 30, 2016 @11:39AM (#13072144)
Redhat also has a lot of security features not in upstream docker due to docker, inc not accepting them:

Source: https://github.com/projectatomic/docker/tree/410e23a7eeb52d4...

Re:Docker and Canonical Partner on Commercially-Supported Do... by justincormack on Wednesday November 30, 2016 @12:52PM (#13072889)
That seccomp patch reduces rather than increases security. None of the others, other than back ports, are security features.
Re:Docker and Canonical Partner on Commercially-Supported Do... by SEJeff on Wednesday November 30, 2016 @02:45PM (#13073990)
Disabling the docker hub certainly is.
Re:Docker and Canonical Partner on Commercially-Supported Do... by justincormack on Wednesday November 30, 2016 @05:38PM (#13075362)
In what way? It changes a default, but it only changes namespaces, not security.