Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker 1.11: The first OCI-compliant runtime, built on containerd

blog.docker.com

Post reply on HN
Print view View original

11–20 of 64 posts

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#11

Post by cpuguy83 »

sams99 wrote: post #8

This is a huge upgrade that is super welcome. Recently (on 1.9) we have seen quite a few cases where we had "zombie" containers, these are container that can no longer be started or stopped due to cgroup misconfiguration or something along those lines. The new architecture means that for weird cases like this all we need to do is kill off runc without forcing every container on the box to restart (by restarting the d…

Sounds likely to be https://github.com/docker/docker/issues/18180

If so, it's a bug with a particular (newer) version of AUFS that has been fixed in most distros.

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#12

Post by sams99 »

cpuguy83 wrote: post #11
sams99 wrote: post #8

This is a huge upgrade that is super welcome. Recently (on 1.9) we have seen quite a few cases where we had "zombie" containers, these are container that can no longer be started or stopped due to cgroup misconfiguration or something along those lines. The new architecture means that for weird cases like this all we need to do is kill off runc without forcing every container on the box to restart (by restarting the d…

Sounds likely to be https://github.com/docker/docker/issues/18180 If so, it's a bug with a particular (newer) version of AUFS that has been fixed in most distros.

most likely that bug, been tracking it, but I think this goes beyond this specific issue. It makes docker a lot more robust when bugs like this pop up in future.

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#14

Post by alex1 »

wmf wrote: post #6
sengork wrote: post #3

Standardisation at the format level will help with portability across different platform implementations.

This "standardization" is pretty kludgey if you have to docker pull then docker export.

I think that's because OCI currently only has a specification for the runtime, not the distributable image. But it seems like as of a few weeks ago, work is underway to standardize the distributable image as well: https://github.com/opencontainers/image-spec

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#15

Post by skj »

shykes wrote: post #5
emdd wrote: post #4

ELI5 the OCI & why it's important? I follow Docker from a distance and find it fascinating.

Disclaimer: I work at Docker. Docker has become a de facto standard for executing programs in a portable sandbox (aka "container"). There were increasing demands for making it a "proper" standard, so last year we donated a spec and reference implementation for a universal intermediary format - a "PDF of containers" if you will, and partnered with the Linux Foundation to manage it. The majority of the industry followe…

As ELI5s go, this seems not well-targeted at 5-year-olds :)

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#16

Post by ysh7 »

shykes wrote: post #5
emdd wrote: post #4

ELI5 the OCI & why it's important? I follow Docker from a distance and find it fascinating.

Disclaimer: I work at Docker. Docker has become a de facto standard for executing programs in a portable sandbox (aka "container"). There were increasing demands for making it a "proper" standard, so last year we donated a spec and reference implementation for a universal intermediary format - a "PDF of containers" if you will, and partnered with the Linux Foundation to manage it. The majority of the industry followe…

Disclaimer didn't say you are the CEO.

I hope this guy does this again here, https://news.ycombinator.com/item?id=11379475

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#17

Post by tveita »

falcolas wrote: post #10

You know, standardization is a great thing. But, fuck, another major release with huge changes... What ever happened to stable architectures with hardening burn in periods? What new bugs are going to creep in due to these huge changes? How is this going to break our work arounds for previous versions? It's a great time to be in operations, containers are a huge step forward, but how are we supposed to be confident in…

If you want something stable I'd stay away from containers and use well-tested technologies like VMs and configuration management.

In my experience many of the tools in the container ecosystem are in the early adopter phase, promising a lot of convenience for some use cases, but too buggy and feature incomplete to really deliver yet. Not to mention the breaking changes and occasional migration to a new tool.

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#18

Post by nindalf »

skj wrote: post #15
shykes wrote: post #5

Earlier quoted context omitted.

Disclaimer: I work at Docker. Docker has become a de facto standard for executing programs in a portable sandbox (aka "container"). There were increasing demands for making it a "proper" standard, so last year we donated a spec and reference implementation for a universal intermediary format - a "PDF of containers" if you will, and partnered with the Linux Foundation to manage it. The majority of the industry followe…

As ELI5s go, this seems not well-targeted at 5-year-olds :)

As is pointed out repeatedly on /r/ELI5, the explanation doesn't need to be for literal 5 year olds.

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#19

Post by [deleted] »

ysh7 wrote: post #16
shykes wrote: post #5

Earlier quoted context omitted.

Disclaimer: I work at Docker. Docker has become a de facto standard for executing programs in a portable sandbox (aka "container"). There were increasing demands for making it a "proper" standard, so last year we donated a spec and reference implementation for a universal intermediary format - a "PDF of containers" if you will, and partnered with the Linux Foundation to manage it. The majority of the industry followe…

Disclaimer didn't say you are the CEO. I hope this guy does this again here, https://news.ycombinator.com/item?id=11379475

[deleted]

Re: Docker 1.11: The first OCI-compliant runtime, built on containerd

#20

Post by molecule »

ysh7 wrote: post #16
shykes wrote: post #5

Earlier quoted context omitted.

Disclaimer: I work at Docker. Docker has become a de facto standard for executing programs in a portable sandbox (aka "container"). There were increasing demands for making it a "proper" standard, so last year we donated a spec and reference implementation for a universal intermediary format - a "PDF of containers" if you will, and partnered with the Linux Foundation to manage it. The majority of the industry followe…

Disclaimer didn't say you are the CEO. I hope this guy does this again here, https://news.ycombinator.com/item?id=11379475

> Disclaimer didn't say you are the CEO.

Correction: not CEO, "Founder, CTO and Chief Product Officer"

https://www.docker.com/company/management

Post reply on HN