4 ms·
> It's based on TUF which is the state if the art in secure content distribution. Sounds great in theory, but there hasn't been much traction on that project,
by falcolas 10y ago
> It's based on TUF which is the state if the art in secure content distribution.
Sounds great in theory, but there hasn't been much traction on that project, at least from their own website, for over 6 months. Not much in terms of peer review of their method, or practical audits of their technology. Even your own audit is over a year old now, despite constant changes to the codebase.
That said, I do recall now when this was announced originally, and I'm glad that it at least exists. That it has skipped my memory makes me wonder why there has been little to no press about it since then. How broadly adopted has this been? Can we get signed images for, say, Ubuntu from docker hub?
> docker pull NAME@DIGEST
A great feature to have. Can you point me at the digest for the ubuntu repo on docker hub?
> serious refactoring which we have been working on
Good to hear. Also, interesting to note that runc still requires root access to make cgroups; I was not aware of this restriction.
> The Docker core engineering team invests more time on hardening than features.
I find this to be an interesting position to take, considering that a core component of docker has been historically re-written with every other release: registry in 1.6, disk plugins in 1.7, networking in 1.9, runc in 1.11. IIRC, networking was re-written again in 1.12, to support yet another version of clustered networking. That's a lot of churn for less than a year and a half worth of time.
> We hope to see you on the github repo, we value bug reports
That hasn't gone well for me in the past.
devicemapper errors in ubuntu 14.04, prior to dynamic linking: not our problem.
devicemapper dropping mounts sporadically: move to overlayfs.
Low level mutexes being shared between containers: that's nodejs' problem.
It's frankly become easier to create and use workarounds like spam-unmounting orphaned devicemapper mounts, or custom-compiling and distributing docker, or disabling docker-managed networking, and so on.
I feel bad for ragging on Docker like this, especially since I do end up using it frequently; but as a system administrator Docker is a nearly daily headache. Our developers love it, but the rest of us... not so much. I guess it's one of those "technologies everyone complains about" vs "technologies nobody uses" things. It's just really frustrating.
- Pyxl101 10y agoDo you have a link to NodeJS sharing mutexes between different containers? I'd be interested to learn more about that.
- bigmac 10y agoIn terms of signing and verification, doing trusted pulls of the official ubuntu image (or any other official image) is quite easy: export DOCKER_CONTENT_TRUST=1 docker pull ubuntu
- falcolas 10y agoCool, that mostly just works (had a socket error the first time I tried). However, there's some usability problems here that I'd like to bring to your attention: - There is no indication that the pull is different; no output from trust verification that it is indeed signed. This means I have to trust that Docker did the right thing, with no means of verification. - Inspecting the image after pulling gives no indication that the image is signed, and gives me no way to do my own signature validation on the image. - It does fail properly when pulling an unsigned image. Yay! - Docker run initiates a connection back to notary, and fails if it can not connect. This makes me uneasy - it makes me wonder what data is passed, how it's being used, what changes are being made according to the response, and so forth. - Using trust is a per-command decision, instead of a daemon setting. - There's no clear method to revoke a signing key if identified to be malicious. - This seems like a good candidate for "secure by default" once some of the usability issues are resolved.
- cyphar 10y ago> I find this to be an interesting position to take, considering that a core component of docker has been historically re-written with every other release: registry in 1.6, disk plugins in 1.7, networking in 1.9, runc in 1.11. To be fair, runC was its own project for quite some time. Docker just switched from importing the runC code to actually running the binaries through containerd as a proxy in 1.11 (a design decision I'm still trying to wrap my brain around, but that's a separate issue).