4 ms·

It's interesting that I've heard this argument repeatedly from people in the Docker world, yet rarely from those who have experience of implementing it in multi

It's interesting that I've heard this argument repeatedly from people in the Docker world, yet rarely from those who have experience of implementing it in multiple organizations (I do). The philosohpical arguments drift away as the money is saved, and the code moves to a microservices architecture anyway as the rank and file 'get it'. In any case, the intention is not to run everything in a container, but simply get from A (snowflake servers) to B (something useful in a container). In short, if 'doing it wrong' saves your business a ton of money, then I'm not sure how wrong that is.

dz0ny 11y ago
Because you are using wrong tools, LXCd?(is/was) written for exactly this purpose.
- zwischenzug 11y ago
  Do you mean this: https://github.com/lxcd/lxcd https://github.com/lxcd/lxcd or something else?
  - baghira 11y ago
    I think he meant LXD, the daemon for managing LXC containers written by Canonical. See https://www.stgraber.org/2015/04/21/lxd-getting-started/ https://www.stgraber.org/2015/04/21/lxd-getting-started/. I guess that the point is that, compared to other solutions, Docker was specifically meant to run with only one service per container instance.
    - zwischenzug 11y ago
      LXD would make more sense, yes. The problem is those other solutions don't have traction. Also, LXD claims to be Ubuntu-specific: http://www.ubuntu.com/cloud/tools/lxd http://www.ubuntu.com/cloud/tools/lxd
      - baghira 11y ago
        Granted, I was not arguing for LXD as a ready for mass deployment tool. And certainy docker at the moment is more popular. However I don't think LXD is ubuntu specific, see https://github.com/lxc/lxd https://github.com/lxc/lxd https://insights.ubuntu.com/2015/03/20/installing-lxd-and-the-command-line-tool/ https://insights.ubuntu.com/2015/03/20/installing-lxd-and-th... I've just compiled it on Fedora 22 and both the daemon lxd and the cli tool lxc seem to work, haven't tested any container however.

dz0ny 11y ago

Because you are using wrong tools, LXCd?(is/was) written for exactly this purpose.

zwischenzug 11y ago
Do you mean this: https://github.com/lxcd/lxcd https://github.com/lxcd/lxcd or something else?
- baghira 11y ago
  I think he meant LXD, the daemon for managing LXC containers written by Canonical. See https://www.stgraber.org/2015/04/21/lxd-getting-started/ https://www.stgraber.org/2015/04/21/lxd-getting-started/. I guess that the point is that, compared to other solutions, Docker was specifically meant to run with only one service per container instance.
  - zwischenzug 11y ago
    LXD would make more sense, yes. The problem is those other solutions don't have traction. Also, LXD claims to be Ubuntu-specific: http://www.ubuntu.com/cloud/tools/lxd http://www.ubuntu.com/cloud/tools/lxd
    - baghira 11y ago
      Granted, I was not arguing for LXD as a ready for mass deployment tool. And certainy docker at the moment is more popular. However I don't think LXD is ubuntu specific, see https://github.com/lxc/lxd https://github.com/lxc/lxd https://insights.ubuntu.com/2015/03/20/installing-lxd-and-the-command-line-tool/ https://insights.ubuntu.com/2015/03/20/installing-lxd-and-th... I've just compiled it on Fedora 22 and both the daemon lxd and the cli tool lxc seem to work, haven't tested any container however.