4 ms·

The nomad[0] team was just discussing today how much effort to put into our rkt support[1] (our support for rkt lags behind our docker support). So far we don'

The nomad[0] team was just discussing today how much effort to put into our rkt support[1] (our support for rkt lags behind our docker support). So far we don't see a lot of evidence of our users taking rkt into production over Docker, but I'm very curious if there's a significant number of users like Julia looking to avoid running docker in production. From a nomad developer standpoint, while building long command strings is a bit awkward compared to calling docker's API, it's quite easy to support new features and manually run generated commands to test our driver's behavior. [0] https://github.com/hashicorp/nomad https://github.com/hashicorp/nomad [1] https://www.nomadproject.io/docs/drivers/rkt.html https://www.nomadproject.io/docs/drivers/rkt.html

philips 10y ago
Hey Michael! Could you email rkt-dev about your questions as well? Particularly around the long command strings. There are other ways to launch rkt containers besides long args. https://groups.google.com/forum/#!forum/rkt-dev https://groups.google.com/forum/#!forum/rkt-dev
- schmichael 10y ago
  Our only question is more of a usage survey. Not sure it's our place to perform those on your mailing list. :) So far the command line building is more pro than con. It's so nice to be able to copy & paste commands out of logs to see exactly how rkt is being run.
skeptic2718 10y ago
As a user, I don't like have two schedulers (nomad/docker) on my nodes. I don't like having two daemons taking care of the overlay network either. And I don't like magic and things that break from time to time. We've had our fair share of broken Docker upgrades.
zie 10y ago
Well, I for one encourage more rkt support in Nomad, it's very awesome!
onestone 10y ago
I for one am definitely looking to replace Docker in production with Rkt. Just waiting for Rkt support in higher-level components (Kubernetes in my case) to mature a bit more.
otterley 10y ago
I'm just waiting for rkt to mature a bit. I personally don't see much value in running the Docker engine in a production context. It adds needless complexity to what should be a relatively simple solution.
cyphar 10y ago
Have you considered adding OCI support to Nomad? Is this something you're interested in? Currently we're working on getting an OCI-powered container runtime that works with k8s called ocid[1]. It'd be really awesome if nomad was interested in getting OCI (or even ocid) to work as a runner as well. :D [1]: https://github.com/kubernetes-incubator/cri-o https://github.com/kubernetes-incubator/cri-o

philips 10y ago

Hey Michael! Could you email rkt-dev about your questions as well? Particularly around the long command strings. There are other ways to launch rkt containers besides long args. https://groups.google.com/forum/#!forum/rkt-dev https://groups.google.com/forum/#!forum/rkt-dev

schmichael 10y ago
Our only question is more of a usage survey. Not sure it's our place to perform those on your mailing list. :) So far the command line building is more pro than con. It's so nice to be able to copy & paste commands out of logs to see exactly how rkt is being run.

skeptic2718 10y ago

As a user, I don't like have two schedulers (nomad/docker) on my nodes. I don't like having two daemons taking care of the overlay network either. And I don't like magic and things that break from time to time. We've had our fair share of broken Docker upgrades.

zie 10y ago

Well, I for one encourage more rkt support in Nomad, it's very awesome!

onestone 10y ago

I for one am definitely looking to replace Docker in production with Rkt. Just waiting for Rkt support in higher-level components (Kubernetes in my case) to mature a bit more.

otterley 10y ago

I'm just waiting for rkt to mature a bit. I personally don't see much value in running the Docker engine in a production context. It adds needless complexity to what should be a relatively simple solution.

cyphar 10y ago

Have you considered adding OCI support to Nomad? Is this something you're interested in? Currently we're working on getting an OCI-powered container runtime that works with k8s called ocid[1]. It'd be really awesome if nomad was interested in getting OCI (or even ocid) to work as a runner as well. :D [1]: https://github.com/kubernetes-incubator/cri-o https://github.com/kubernetes-incubator/cri-o