3 ms·

Put up a sentence or two of informative discussion, or links or any kind, this is not any kind of way to advance the state of a thread. "Go on, try it" doesn't

by yebyen 10y ago

Put up a sentence or two of informative discussion, or links or any kind, this is not any kind of way to advance the state of a thread. "Go on, try it" doesn't help me in any way. I believe that Docker has more attention, you might call it hype. I'd say "eyes" instead. We have here a way to shown to run everything in Docker, parent link of thread (RancherOS.) That's great, I already went ahead and tried it. I'm still waiting to be convinced that I should try nspawn instead. Without your help, I won't even know what OS Distro I can download to try it, let alone why it's better.

digi_owl 10y ago
Docker also is less invasive. You do not need to build the distro around docker to use docker...
- jvoorhis 10y ago
  This hasn't always been so, as historically a kernel patched to support aufs was a requirement. It's easier to install docker in 2017 as much of the plumbing shared by the container ecosystem (including nspawn) has become ubiquitous.
JdeBP 10y ago
You do not know an operating system that has systemd? Given https://news.ycombinator.com/item?id=13715574 https://news.ycombinator.com/item?id=13715574 that seems very improbable.
- yebyen 10y ago
  I was fishing for an example of any OS or orchestrator that uses systemd-nspawn. [1] shows me how to run systemd-nspawn by itself. [2] shows me that it's basically just like chroot when it comes to a user experience. When do I get to the part that's better than the entire ecosystem of schedulers and orchestration tools that has sprung up built on and around Docker? Are all of those companies wrong? (Are you trying to tell me it's all just hype and I should put everything into the hands of one competent sysadmin that manages nspawn and systemd?) I could be convinced of that, but I just don't see anyone doing that. I guess that's actually what was meant by cargo cult. This all really just makes me want to go out and spend some more time looking at Rkt instead. We're all not even remotely convinced that this is better. Where is the mantl.io built on systemd-nspawn? [1]: https://wiki.archlinux.org/index.php/Systemd-nspawn https://wiki.archlinux.org/index.php/Systemd-nspawn [2]: https://rich0gentoo.wordpress.com/2014/07/14/quick-systemd-nspawn-guide/ https://rich0gentoo.wordpress.com/2014/07/14/quick-systemd-n... Edit: I am still going to upvote you because you went to the trouble of going through my post history.

by yebyen 10y ago

digi_owl 10y ago

Docker also is less invasive. You do not need to build the distro around docker to use docker...

jvoorhis 10y ago
This hasn't always been so, as historically a kernel patched to support aufs was a requirement. It's easier to install docker in 2017 as much of the plumbing shared by the container ecosystem (including nspawn) has become ubiquitous.

JdeBP 10y ago

You do not know an operating system that has systemd? Given https://news.ycombinator.com/item?id=13715574 https://news.ycombinator.com/item?id=13715574 that seems very improbable.

yebyen 10y ago
I was fishing for an example of any OS or orchestrator that uses systemd-nspawn. [1] shows me how to run systemd-nspawn by itself. [2] shows me that it's basically just like chroot when it comes to a user experience. When do I get to the part that's better than the entire ecosystem of schedulers and orchestration tools that has sprung up built on and around Docker? Are all of those companies wrong? (Are you trying to tell me it's all just hype and I should put everything into the hands of one competent sysadmin that manages nspawn and systemd?) I could be convinced of that, but I just don't see anyone doing that. I guess that's actually what was meant by cargo cult. This all really just makes me want to go out and spend some more time looking at Rkt instead. We're all not even remotely convinced that this is better. Where is the mantl.io built on systemd-nspawn? [1]: https://wiki.archlinux.org/index.php/Systemd-nspawn https://wiki.archlinux.org/index.php/Systemd-nspawn [2]: https://rich0gentoo.wordpress.com/2014/07/14/quick-systemd-nspawn-guide/ https://rich0gentoo.wordpress.com/2014/07/14/quick-systemd-n... Edit: I am still going to upvote you because you went to the trouble of going through my post history.