Docker 1.11: The first OCI-compliant runtime, built on containerd • Hacker News Board

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

#61

Post by solarengineer » Fri, Apr 15, 2016, 2:52 AM UTC

mhotchen wrote: post #35

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…

There's also these: - https://runc.io/ - https://linuxcontainers.org/ And I'm not sure if they're the same thing, compatible, or what. I'm going to let someone else pick the winner for me. I'll come back to containers in like a year or so and see what the lowdown is.

Plus, there's FreeBSD Jails, Illumos Zones, and SmartOS' support for Linux apps (Dockerized or otherwise). SmartOS is based on Illumos.

I was reading the recent HN discussion + article on the recent network namespaces, and wondered at how much ahead networking on Illumos is.

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

#62

Post by esseti » Fri, Apr 15, 2016, 6:36 AM UTC

falcolas wrote: post #52

thresh wrote: post #50

Earlier quoted context omitted.

You can use nginx to have zero-time redeployments without gross hacks haproxy requires to do that.

I would also recommend nginx. For pure proxying it's rather convenient, and offers some nice high level caching if you desire it.

But to use nginx i've to recreate the container to link the new "web4" container. don't I? and then to make it reload the conf. or is there anything else that i can do?

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

#63

Post by emdd » Sat, Apr 16, 2016, 12:30 AM UTC

nindalf wrote: post #18

skj wrote: post #15

Earlier quoted context omitted.

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.

Correct. It's not literal, and I didn't mean it literally (I don't think anyone actually does). I would probably have not been happy if that was the only type of answer. Maybe, we will say ELI16? Kidding. No, don't do that.

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

#64

Post by skj » Sat, Apr 16, 2016, 1:54 AM UTC

nindalf wrote: post #18

skj wrote: post #15

Earlier quoted context omitted.

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.

I'm aware, but I felt like shykes was simply repeating the copy from the blog post without actually breaking it down into simpler pieces. A sibling post did much better.