6 ms·

Still true: https://xkcd.com/927/ https://xkcd.com/927/

bhhaskin 11y ago
I have been seeing this posted all over HN as of late. Although it is funny, it doesn't really add anything to the conversation...
- falcolas 11y ago
  It points out, in the typical form of humor, that we're going to take a N wheels (the container spec in this case), try and shove them together, to get N+1 wheels. And this is relevant in a space with at least 4 competing standards (and one dominant one). In the short term, what Docker uses with will matter more than the output of any such committee. In the long term, well, it depends on Docker-the-company's fate.
  - jessaustin 11y ago
    Might TFA be a portent for the medium term? The big players who hope to squash Docker are embracing now, only to extend later?
  - jsmthrowaway 11y ago
    > In the short term, what Docker uses with will matter more than the output of any such committee. How is that true? I'm already excited to kill dockerd just to run containers.
    - falcolas 11y ago
      Many container services currently support starting Docker images, and with all of the money spent on marketing, Docker also owns the container ecosystem mindshare. It's their game to lose.
  - bhhaskin 11y ago
    Now that adds to the conversation. I think it is fine to use it to illustrate a point, but it doesn't stand alone by itself.
    - kzhahou 11y ago
      It's exactly what the xkcd already illustrated, though more verbosely. I see nothing wrong in using imagery as shorthand to express an idea.
bmurphy1976 11y ago
That's horse-crap. There is no standard in this case. That we even have a first stab at a standard is a good thing.
- falcolas 11y ago
  Aside from Docker containers (which are broadly consumed by competing container engines), rkt containers, the systemd "Container Interface" specification, and the LXC containers, you're right. There's no standard. /s
  - icebraining 11y ago
    From what I can tell, systemd's interface is not a container spec, but a way for Docker et all to launch systemd inside their own containers. And LXC doesn't define a container format either, it's more of a lower-level API, which is why Docker itself can use it to run their own containers.
    - nailer 11y ago
      > a way for Docker et all to launch systemd inside their own containers. Should that read: "a way for Docker et all to launch systemd units inside their own containers." ?
      - icebraining 11y ago
        No, from what I can tell, it's actually to launch systemd itself inside a container. For example, from the document: To allow systemd (and other code) to identify that it is executed within a container, please set the $container= environment variable for PID 1 in the container to a short lowercase string identifying your implementation. With this in place the ConditionVirtualization= setting in unit files will work properly. Example: "container=lxc-libvirt"
    - vezzy-fnord 11y ago
      systemd itself has its own system container tool called nspawn, though again like LXC it doesn't have any image format, serialization or anything of the sort. rkt originally used nspawn as its backend (still has it in, I think).
msoad 11y ago
That's true for lodash + underscore merger which led to a new library but it's not true here!
deleted 11y ago
[deleted]

I have been seeing this posted all over HN as of late. Although it is funny, it doesn't really add anything to the conversation...

falcolas 11y ago
It points out, in the typical form of humor, that we're going to take a N wheels (the container spec in this case), try and shove them together, to get N+1 wheels. And this is relevant in a space with at least 4 competing standards (and one dominant one). In the short term, what Docker uses with will matter more than the output of any such committee. In the long term, well, it depends on Docker-the-company's fate.
- jessaustin 11y ago
  Might TFA be a portent for the medium term? The big players who hope to squash Docker are embracing now, only to extend later?
- jsmthrowaway 11y ago
  > In the short term, what Docker uses with will matter more than the output of any such committee. How is that true? I'm already excited to kill dockerd just to run containers.
  - falcolas 11y ago
    Many container services currently support starting Docker images, and with all of the money spent on marketing, Docker also owns the container ecosystem mindshare. It's their game to lose.
- bhhaskin 11y ago
  Now that adds to the conversation. I think it is fine to use it to illustrate a point, but it doesn't stand alone by itself.
  - kzhahou 11y ago
    It's exactly what the xkcd already illustrated, though more verbosely. I see nothing wrong in using imagery as shorthand to express an idea.

bmurphy1976 11y ago

That's horse-crap. There is no standard in this case. That we even have a first stab at a standard is a good thing.

falcolas 11y ago
Aside from Docker containers (which are broadly consumed by competing container engines), rkt containers, the systemd "Container Interface" specification, and the LXC containers, you're right. There's no standard. /s
- icebraining 11y ago
  From what I can tell, systemd's interface is not a container spec, but a way for Docker et all to launch systemd inside their own containers. And LXC doesn't define a container format either, it's more of a lower-level API, which is why Docker itself can use it to run their own containers.
  - nailer 11y ago
    > a way for Docker et all to launch systemd inside their own containers. Should that read: "a way for Docker et all to launch systemd units inside their own containers." ?
    - icebraining 11y ago
      No, from what I can tell, it's actually to launch systemd itself inside a container. For example, from the document: To allow systemd (and other code) to identify that it is executed within a container, please set the $container= environment variable for PID 1 in the container to a short lowercase string identifying your implementation. With this in place the ConditionVirtualization= setting in unit files will work properly. Example: "container=lxc-libvirt"
  - vezzy-fnord 11y ago
    systemd itself has its own system container tool called nspawn, though again like LXC it doesn't have any image format, serialization or anything of the sort. rkt originally used nspawn as its backend (still has it in, I think).

msoad 11y ago

That's true for lodash + underscore merger which led to a new library but it's not true here!

deleted 11y ago

[deleted]