15 ms·
Running containers without Docker
- moondev 10y agoWhat is the motivation and benefit for running containers without docker? Docker is by far the more mature and adopted development tool. It also runs great on windows, macos and linux. While k8s can run containers via the rkt runtime, it's still pretty new and will probably introduce unnecessary headache and edge cases. Docker also has a head start on a vibrant ecosystem for base images. In my opinion it would be better to focus on docker, and when rkt gets there it shouldn't be much of an issue to switch if desired.
- jsmthrowaway 10y agoContainers existed before Docker and will exist after Docker, and articles like these are desperate attempts to remind everyone of that in the face of Docker's unilateral destruction of the concept. I know I'm right because of comments like these that presuppose "well, if you're doing containers, use Docker, the alternatives just aren't there." Except they were, before Docker, and after Docker. Docker is a developer tool, not a container runtime. The 'containers' it presents require you to commit a daemon on every machine, commit to a weird storage and distribution story when, you know, files of containers served in a flat directory are totally adequate, and so on. Docker made extremely complicated choices for a lot of things and now everybody wishing to advance containers has to deal with presuppositions like these, where Docker exists and the motivation for not using it is unclear to a lot of people, you included.
- twblalock 10y agoDocker is a container runtime, not merely a developer tool. It was intended as such from the beginning. It is successfully used in production at large scale by a number of companies, including Uber. The fact that you don't like Docker doesn't change any of that. If you don't like it, don't use it. But there is no justification for you to claim it is only a developer tool when it is obviously more than that.
- secstate 10y agoDocker was originally built on top of LXC. It is now becoming more flexible with what is underneath, but there's a reason you need a VM running in the background on macOS to use Docker. Docker is tool to interact with LXC (and hopefully other container systems).
- icebraining 10y agoDocker doesn't use LXC anymore[1]. The reason you need a VM is to get the Linux kernel, not LXC, and the reason you need that is because the macOS kernel (Darwin) doesn't have the necessary containerization features. On FreeBSD, for example, Docker runs natively, without a VM. [1] https://www.infoq.com/news/2014/03/docker_0_9 https://www.infoq.com/news/2014/03/docker_0_9
- fnj 10y agoIf MacOS doesn't have certain linux kernel features, neither does FreeBSD. How can Docker run on FreeBSD when FreeBSD has no cgroups? I think you misread/misinterpreted your reference.
- tonyhb 10y agoxhyve and bhyve virtualization built into the BSD kernels. docker for mac now runs a tiny linux vm directly on osx
- 2trill2spill 10y ago> How can Docker run on FreeBSD when FreeBSD has no cgroups? I think you misread/misinterpreted your reference. FreeBSD can run 64 bit and 32 bit Linux binaries via it's Linux emulator[1]. Plus FreeBSD has had containers since FreeBSD 4 which was released in March of 2000, except containers on FreeBSD are called jails. > If MacOS doesn't have certain linux kernel features, neither does FreeBSD. Just because one operating system doesn't have a feature that does not mean a different operating system does not have that feature. [1] https://www.freebsd.org/doc/handbook/linuxemu.html https://www.freebsd.org/doc/handbook/linuxemu.html
- moondev 10y agoSo what is your alternative? Run containers your own unique way and roll your own distribution mechanism and networking to fragment yourself from the tools in the "container" space?
- ex_amazon_sde 10y agoWhen "your own unique way" requires less development time and efforts and it's easier to learn for new hires, yes. That's why you hire system engineers - to write good automation.
- philips 10y agoJust to clarify two things: - rkt can run any docker image in the vibrant ecosystem: https://coreos.com/rkt/docs/latest/running-docker-images.html https://coreos.com/rkt/docs/latest/running-docker-images.htm... - Help test Kubernetes and rkt with minikube, it is working nicely today: https://github.com/kubernetes/minikube#using-rkt-container-engine https://github.com/kubernetes/minikube#using-rkt-container-e...
- sysexit 10y ago> What is the motivation and benefit for running containers without docker? I believe that Docker bet the company on the wrong business model. Therefore knowing that you can run containers without Docker can be desirable, as it gives you options in case Docker turns out to be not viable. Docker made it easy to build and run containers from the command line. This technology was released at the right time and in the right place. And it got huge traction. Docker used this traction to get a very large amount of VC capital. Therefore they now need to show a very large return. How do you go about achieving that large return? A common way to do this is to use one piece of technology that is popular as an anchor to lock customers into an entire stack. And then you monetize the stack, which is easier as it has higher value. The technology in this case is the container runtime, and the stack would be an full enterprise grade container orchestration system. This strategy worked for others. Microsoft was a master in this. VMware as well, and so is Oracle. The reason I believe it will not work for Docker is: 1. The anchor technology is open source. Microsoft managed their lock-in via Windows, VMware via ESX, Oracle via their DB. It worked because those are proprietary. In the open source world you can just take Docker. 2. Even though the technology is open source, you can still try the ecosystem approach where you exploit certain network effects attached to your distribution of the code that protect you (e.g. vendor certifications). This is what worked for Red Hat. In my view it is unlikely to work for Docker. I don't think certifications are required as most container apps today are not vendor apps. And I would not know what else they could use. 3. For orchestration solution they are engineering against Google's Kubernetes. With all respect for Docker, this is going to be very hard as Google has a huge amount of experience in this area. 4. Due to Docker's need to protect their business model, there is no true community in the sense that there is an open exchange of ideas. The docker agenda prevails over technical decision making (like: should you have a docker daemon? Should Swarm be part of the Docker Engine?). Contrast that with Kubernetes which run in a very open manner by Google. This is why OpenStack got the traction, and why Eucalyptus and CloudStack died off. OpenStack had the most open community. All of this can lead, IMHO, to a situation where Docker will not succeed in delivering Swarm as they see it. Kubernetes will become the default container orchestration system, and Docker is relegated to a small place in the stack. This situation would make it hard for Docker to justify their valuation.
- jacques_chester 10y ago
- deleted 10y ago[deleted]
- shykes 10y agoDocker founder here. > What is the motivation and benefit for running containers without docker? I regularly hear from people who want to run containers without Docker. There are several motivations, all of which are perfectly valid: 1. Learning. It's fun to build things from scratch to understand how they work under the hood. 2. Bad experience. Early versions of Docker were quite buggy, and we initially struggled to keep up with the colossal growth in usage and feature requests. As a result, many of the people who tried Docker in production too early were badly disappointed. Some of them decided Docker wasn't for them, and started looking for alternatives. 3. Extremely custom use case. If your deployment is larger, or more complex, or more specialized than 99.99% of deployments out there, then "mainstream" platforms like Docker might not be the right fit for you. Of course we try to make Docker as customizable as possible, to support more a wider spectrum of use cases with plugins. But realistically, no single platform can cover all use cases, and I don't think any platform ever will. Docker is no exception. 4. Philosophy disagreement. Different people have different opinions on how applications should be developed and deployed. Docker tries very hard to be agnostic - to accommodate as many opinions as possible. But we can't please everybody. If Docker does not fit your philosophy of development and deployment, then the natural response is to look for an alternative. 5. Competition. Many Docker competitors started out as extensions or modifications of Docker, and over time are looking to reduce their dependency on Docker. I'm probably missing other reasons, but these are the ones I've been most exposed to. These are all reasonable reasons to not want to use Docker. Our approach is that, if you want to run containers without Docker, we should make it as easy as possible. In practice that means spinning out as many of the underlying components as possible (what we call the "plumbing") so that you can assemble it yourself without being stuck using the entire Docker platform. For example: - containerd [https://github.com/docker/containerd https://github.com/docker/containerd] is our low-level container runtime. - runc [https://runc.io https://runc.io] is a standardized "container executor", which we donated to the Linux Foundation as the reference foundation for the OCI spec. - libnetwork [https://github.com/docker/libnetwork https://github.com/docker/libnetwork] is the low-level networking implementation (including overlay networking which is a very useful primitive for container clustering) - swarmkit [https://github.com/docker/swarmkit https://github.com/docker/swarmkit] is a clustering/orchestration implementation - notary [https://github.com/docker/notary https://github.com/docker/notary] is a cryptographic content verification tool, which you can use to sign and verify container images. - infrakit [https://github.com/docker/infrakit https://github.com/docker/infrakit] automates the provisioning of infrastructure capable of running containers. Our opinion is that, even if you don't use Docker, by using these components for your own purposes, you are indirectly contributing to making Docker better. Splitting out these components has also forced us to refactor Docker into a more modular, more robust design. We even send Docker employees to explain how to run containers without Docker :) For example here's a talk we gave at Linuxcon: https://linuxconcontainerconeurope2016.sched.org/event/7oHM/building-distributed-systems-without-docker-using-docker-plumbing-projects-patrick-chanezon-docker https://linuxconcontainerconeurope2016.sched.org/event/7oHM/...
- zzzcpan 10y agoRecently tried to run docker on Ubuntu Desktop 14.04. After googling a bunch of errors, trying different versions, but still failing decided to try rkt. That one worked out of the box, but apart from a bunch of simple images failed to run the caffe docker image. So, my motivation of running without docker would be to understand every little thing they do to actually be able to use them and rely on them.
- moondev 10y agocurl -sSL https://get.docker.com/ https://get.docker.com/ | sh sudo usermod -aG docker $your_user There ya go. In newer distros its as easy as apt-get install docker.io
- zzzcpan 10y agoIt installs fine, it just doesn't work. There is an issue on github with the same errors as I saw, where they discuss not fixing it, because of how uncommon the system is.
- imtringued 10y agoAdding a user to the dockergroup is a bad idea on a desktop.
- cakeface 10y agoThe motivation is to make a smaller change to their operations and infrastructure. Right now they are running application services on linux machines using puppet to make the machine environment work. Switching to a container gives them reproducible environments that work on a developer workstation and a server. It also gives some operational benefits for how you run a process I think. You can do this without buying into the docker daemon, network overlay, orchestration. If you are currently able to deploy services on linux to production then you can do that, but with containers. This is an incremental win.
- deleted 10y ago[deleted]
- jsmthrowaway 10y agoI've successfully used Docker in production since it was a hobby project of dotCloud. I was answering the OP's question about why anybody would ever consider not using Docker for containers, so it's ironic that I'm now responding to your comment as the followup about my personal preferences. Clever commentary trap: why not? Here's why. Oh, well, nobody's forcing you to use it.
- twblalock 10y agoThis is what you wrote: > Docker is a developer tool, not a container runtime. It's just not true, and that's why I responded.
- jsmthrowaway 10y agoThe bloody comment I replied to called it that, and it's not controversial. Docker did not suggest running in production for many years and the production stuff is largely an afterthought. Again, I developed this opinion from running it for years. It was not intended for production usage from the beginning, as you claimed, but I'm already tired of responding to this thread because I'm turning instantly gray for not buying into Docker so why would I bother proving that you're not correct?
- twblalock 10y agoYou called it that. Read what you wrote. Here, I'll paste your entire comment as it is now, since you keep editing it: > Containers existed before Docker and will exist after Docker, and articles like these are desperate attempts to remind everyone of that in the face of Docker's unilateral destruction of the concept. I know I'm right because of comments like these that presuppose "well, if you're doing containers, use Docker, the alternatives just aren't there." Except they were, before Docker, and after Docker. > Docker is a developer tool, not a container runtime. The 'containers' it presents require you to commit a daemon on every machine, commit to a weird storage and distribution story when, you know, files of containers served in a flat directory are totally adequate, and so on. Docker made extremely complicated choices for a lot of things and now everybody wishing to advance containers has to deal with presuppositions like these, where Docker exists and the motivation for not using it is unclear to a lot of people, you included. See the first sentence in the second paragraph? That's you. You wrote that. You did not present it as an opinion, but as a fact.
- schmichael 10y agoThe 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 agoHey 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 agoOur 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 agoAs 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 agoWell, I for one encourage more rkt support in Nomad, it's very awesome!
- 10y ago
- alex- 10y agoI was introduced to linux cgroups and namespaces via my use of docker. It is a fantastic tool for using these concepts quickly and I don't currently see rocket etc overthrowing dockers dominance in the market place. However I do sense (and feel my self at times) a growing upset with the usability/ stability of the docker engine. The OCI (Open Container Initiative) should allow new solutions to come to market without fragmenting the space. i.e. it should be possible to run any image with any container engine/Linux. Docker is valued at $1B. It appears that justifying that valuation has taken them into a number of adjacent markets. I wish they were more focused on the Docker Engine itself.
- elsonrodriguez 10y agoThat's the main issue with Docker right now. They've built an amazing static compiler that works with any language, but there's a question as to whether that compiler is worth 1B.
- wlamartin 10y agoYep, the OCI is doing great stuff. At the bottom of the Cloud Foundry stack we have Garden-Runc (https://github.com/cloudfoundry/garden-runc-release https://github.com/cloudfoundry/garden-runc-release). In past we had our own homegrown containerization technology and we're super happy to have been able to swap that out entirely in place of runc - it allows us to make use of the significant engineering talent contributed and has enabled us to move faster and reduce risk. We're also buying into the image-spec for this reason. Right now the focus is in underpinning CF, so although it is production ready functionally, it lacks the pretty fantastic user experience that Docker brings. Perhaps allowing us to reduce our focus on the containerizer, we'll be able to spend more time improving UX - which would be neat. I believe the Kubernetes team is working on a simple implementation of the Kube API which is a thin wrapper around runc as well - so you're right, there are some cool things coming around as a result of the OCI.
- cyphar 10y ago> Yep, the OCI is doing great stuff. At the bottom of the Cloud Foundry stack we have Garden-Runc (https://github.com/cloudfoundry/garden-runc-release https://github.com/cloudfoundry/garden-runc-release). In past we had our own homegrown containerization technology and we're super happy to have been able to swap that out entirely in place of runc - it allows us to make use of the significant engineering talent contributed and has enabled us to move faster and reduce risk. Hi! I'm one of the maintainers of runC and I wanted to say that the CF stuff around runC is awesome. Keep it up. :D > I believe the Kubernetes team is working on a simple implementation of the Kube API which is a thin wrapper around runc as well - so you're right, there are some cool things coming around as a result of the OCI. Actually, ocid is mostly being worked on by people from the OCI community (runcom, mrunalp, myself and others). Though we are getting support from the Kubernetes folks with it, which is pretty cool. :D
- patrickg_zill 10y agoIf someone sent me an email equivalent to this blog post, my sole recommendation would be ProxMox running OpenVZ. OpenVZ gets you 90% of the way to Docker-style containers without breaking anything for her developers.
- icebraining 10y agoThe current version of Proxmox uses LXC instead of OpenVZ, which is interesting since it's using the same kernel containerization features that Docker uses, unlike OpenVZ which required a custom kernel.
- patrickg_zill 10y agoMy mistake- I thought they had the option to use KVM, LXC, or OpenVZ all at once. I see now that in adding LXC they dropped OpenVZ.
- ifhs 10y agoI thought openvz was deprecated.
- Thaxll 10y agoWell you can run a single binary in a solution like Mesos or Kubernete. afaik it's what Google is doing. It's also how Hadoop and other m/r work.
- random567 10y agoI don't get the differentiation between "rkt" and "docker". What complexity does Docker add? Separate networking? Difficulty communicating between processes? Just trying to understand why rkt is less overhead...
- schmichael 10y agoOne large difference is that docker has a daemon that exposes an HTTP API and acts more or less like an init for containers. The docker daemon has historically had some stability issues as well as some security implications. Running a command line tool like rkt is a vastly smaller attack surface and less complex stack overall.
- orthecreedence 10y agoAlso, not sure if this is still the case, but Docker's daemon ran as root on the host. Any vulnerability has the potential to give root on the host machine to an attacker. I don't think this has ever happened, but rkt's approach of using a process per container just makes much more sense in a security context (and for containerization in general).
- fapjacks 10y agoThe daemon needs superuser privileges to do its business, but your containers are not running as root. That lives behind the --privileged option and has ample guidance in the documentation against using it.
- TheDong 10y agoWrong. Without usernamespacing your containers do run as root. If you type `docker run busybox id` it will print uid=0, and that uid is 0 in the container and out of it. You are namespaced, so the linux kernel promises that even though you're root, you're not dangerous, and there is syscall filtering and shit going on.... but that historically has not really fared that well! But your statement is false. You're root with and without privileged. Privileged gives you back CAPABILITIES which are different than USER, so your claim is bullshit.
- masterleep 10y agoTry systemd containers (e.g, systemd-nspawn) if you're on a systemd distro like Ubuntu 16.04.
- aorth 10y agosystemd-nspawn is great! The workflow feels much more native than Docker on GNU/Linux host. The easy integration with networking, BTRFS snapshots, etc is very powerful.
- otterley 10y agoPlease upvote my feature request for zfs snapshot support! https://github.com/systemd/systemd/issues/4272 https://github.com/systemd/systemd/issues/4272
- Torgo 10y agoWhen I "discovered" systemd-nspawn, I kept thinking "why aren't people using this? This is easier to understand in every way."
- dln_eintr 10y agorkt actually uses systemd-nspawn to run and namespace the container. What rkt "adds" before that is downloading, verifying managing the container image and setting up the cgroup for resource limitation. https://github.com/coreos/rkt/blob/master/Documentation/devel/architecture.md https://github.com/coreos/rkt/blob/master/Documentation/deve...
- masterleep 10y agoDoesn't systemd do that already (via machinectl, e.g.)?
- apeace 10y agoI have to say: before I began to read through, I was already convinced the author's idea was not a good one. But by the time I finished, she convinced me that it was a good plan in her situation. There are lots of great tools in the Docker/container ecosystem these days, but I can see the argument that a major infrastructure migration should be done in incremental steps. Using containers as simply a Puppet replacement strikes me as a really good idea! You want your application to be _ready_ for containerization, before you try to introduce an orchestration system. Although, when she mentioned that her team is meant to be "Heroku for the rest of the company", I couldn't help but think of Convox [0]. It's a great tool, it's open-source, and using it is really just like having your own Heroku. We used Convox at my last company, had amazing success with it, and I've been recommending it ever since. [0] https://jvns.ca/blog/2016/10/26/running-container-without-docker/ https://jvns.ca/blog/2016/10/26/running-container-without-do...
- daeken 10y agoFYI, your link is pointing to the OP. I think you meant https://convox.com/ https://convox.com/
- apeace 10y agoThank you! Caught this too late to edit.
- nzoschke 10y agoConvox founder here. Thanks for the shout out! We are indeed building a private Heroku like platform so you don't have to. It's a simple of layer around AWS so it doesn't add extra craziness some other approaches do. As for the OP, her approach is spot on! Containerizing your app is the first step in future proofing it. Doing so correctly will remove layers and therefore simplify things. You now are looking at a package that can run on a laptop and run on a server with traditional techniques (upstart, systemd, etc). You may take this to the next step and enter the orchestration world. Or not! Patience is a virtue, wait 6 more months and all the orchestration tools will be that much better. It's all about simplifying. Adopt Dockerfile and shed Homebrew and Chef. Run containers on a "dumb" box with systemd and shed Packer. Run containers on ECS and shed custom AMIs and userdata and nagios and...
- throw2016 10y agoI think when it comes to containers HN has been guilty of a shocking lack of scrutiny and unilaterally hyping Docker. For example Docker was based on LXC till 0.9 but was so successful in hype and misdirection of the project it's based on that till today most commentators here do not seem to have a proper idea of the LXC project and whatever ideas they have are negative. How did this come to be? I don't know how healthy it is for open source if the HN community lets VC funded projects essentially hijack open source projects in this way and allow misconceptions to grow about them. For the record LXC has always been a full scale container manager and was and remains a much simpler way to use containers than Docker. Most of the big problems holding back containers like security, isolation, multi-tenancy are kernel side and not container manager side or ecosystem side and will be solved kernel side. Similarly most of the features of containers that are usable today are also thanks to kernel side. Yet the folks who work on kernel namespaces, aufs, overlayfs and other container used technologies receive no rewards or even recognition while companies like Docker completely reliant on their work suck up the attention and hype. How is this sustainable? How many know the author of Aufs or Overlayfs? How much support have these projects received and how do these projects sustain themselves. How many know that cgroups were not namespaced, the issues this created for containers and that they recently got namespaced? How many know about the fantastic advantages but also pitfalls of user namespaces? Isn't this the kind of 'container discussion' we should we having on HN instead of Docker or vendor focussed discussions? And thanks to the lack of scrutiny, Dockers complex use case of containers has passed unexamined and worse been conflated to containers. This has only increased technical debt for users just stepping in and runs the risk of putting users off containers due to the inherent complexity.
- tlrobinson 10y agoDocker is a case where "the whole is greater than the sum of its parts". Yes, LXC and cgroups and aufs and overlayfs and whatever else do a lot of the heavy lifting, but Docker glued it all together in a way that was approachable by any developer, not just Linux geeks. I remember briefly looking into LXC ~6 years ago and being totally lost. Then Docker came along with a simple command line interface and growing repository of images. If you want to be popular among developers, the "hello world" developer experience should be extremely simple. See: Stripe, Twilio, Docker, GitHub, etc. That said, I do think it's too bad that the Docker client/daemon are the lowest-level building block most people are interacting with. It doesn't seem to follow the Unix philosophy of doing one thing well.
- girvo 10y agoWe followed this idea at my workplace! It worked wonderfully; we slowly containerised every project we have, then deployed the containers as "dumb" "programs". Yesterday I began the orchestration step, and everything has gone extremely smoothly. Altogether this has taken about 12 months of on-and-off work, maybe a man-month all up.
- sciurus 10y ago> I think that just using containers by itself will force us to be disciplined about how we package and run services (you have to install all the stuff the service needs inside the container, otherwise the service will not work!). > > There’s no way for it to silently depend on the host configuration, because its filesystem is totally separate from the host’s filesystem. I don't buy this, at least as presented. /etc/awesome/blah.xml does not spontaneously come into existence on a host on its own. No matter if you're building a docker image, a VM image, or managing long-lived hosts via a configuration management tool, you have to specify that /etc/awesome/blah.xml is created and has certain contents. It sounds like the author is working on a poorly structured and documented puppet codebase, where all the dependencies of services aren't clear. Presumably if they can figure them out in order to build working docker images, they could also figure them out and then refactor the Puppet code to make it more maintainable. At that point they could use their puppet code to generate their docker images, which fits nicely into the "horizontal change" philosophy.
- peterwwillis 10y agoSo, in general, tools like Docker are crap because they're like the Apple iPod equivalent of old standard Unix-style tools: bloated monolithic slapped together crap that's crammed with non-extensible non-intuitive extras, designed for people who don't want to know anything about how the sausage is made. But if you do want to do fancy production things, it's nice to have a tool that thousands of people have used for thousands of different things, and bake in all the weird fixes for weird problems over thousands of iterations of testing and bug-fixing. However. If what you want is to simply understand what's going on under the hood, this is a great way to do it. The only thing better that I would recommend is to actually make your own Docker. It's not that difficult, you're basically just slapping together some system calls and execvp()ing some other standard tools, which is what Docker does, and you don't need to support any of the extra fancy features. But you gain an intimate understanding of what could be going on when stuff in production is breaking.
- tarmstrong 10y ago> The only thing better that I would recommend is to actually make your own Docker. It's not that difficult, you're basically just slapping together some system calls and execvp()ing some other standard tools, which is what Docker does Not sure if you've seen this, but the author wrote a great post about the Linux primitives that Docker is built on: http://jvns.ca/blog/2016/10/10/what-even-is-a-container/ http://jvns.ca/blog/2016/10/10/what-even-is-a-container/
- cyphar 10y agoNote that you can use runC (the underlying runtime for Docker) in a similar way to rkt (except you also don't have to deal with images if you don't want to -- runC just runs a rootfs). And runC doesn't have a daemon as well, and is the canonical implementation of the Open Container Initiative runtime specification. We're also working on ocid, which is a way to run kubernetes purely on an OCI stack (no Docker required). Though, shoutouts to the rkt guys. They really are awesome and have been helping out a lot in the OCI effort.
- heavenlyhash 10y ago> you also don't have to deal with images if you don't want to -- runC just runs a rootfs Which is an awesome and powerful thing! The ability to define a filesystem without any middle men simply makes some integrations possible. Thank you and everyone on the runC team so much for your work.
- iuhgdwij 10y agoIf the author reads this, she might want to run this in vim :s/build a comtainer image/build a container image/g to fix a spelling error
- dustinmoris 10y agoI don't get the author. So to sum it up, they like what Docker did with containers, but they don't want to use Docker, at least not immediately, because it requires to learn a few Docker commands and a bit other stuff and therefore they decided to build their own hybrid shit, which will take them probably more time to build than to learn Docker and then on top of that still need to train their employees on that as well, instead of using a well working, vibrant, healthy eco system, build by someone else, for free? I cannot help myself but that sounds like the worst idea ever and totally backwards. Particularly when they she said that they want to run containers reliably in production, how do they think they are going to do this? The reason why Docker is a "little" bit more than just `Docker run` is so you can run containers reliably and in case of a fail over recover quickly. So how are they planning to run containers reliably in production without adopting an existing, well tested, well working framework?
- fauigerzigerk 10y ago>Particularly when they she said that they want to run containers reliably in production, how do they think they are going to do this? As I understand it, they keep doing what they have been doing all along, including everything that currently makes their system reliable, and gradually add some of the desirable features of containers in a way they can fully understand. That doesn't sound like the worst idea ever to me. The danger of ending up with too much of a homegrown snowflake is of course real. You're not wrong about that. But she described the risks of the alternative approaches pretty well I think.
- dustinmoris 10y agoI don't get what the issue is with the migration plan to Docker either. You have a big system with many components. The best way to start is build a Hello world app on Docker and orchestrate it with whatever framework you think suits best your requirements, let's say Kubernetes. Then run that hello world stuff for a while to get a POC and make yourself familiar with the sytem. After that start converting 1 of the many services to a dockerized service and run it side by side in your new infrastructure. Maybe even load balance some of the traffic progressively over to the new stuff until you are confident enough to run 100% load on that migrated servcie. By then you should be pretty experienced with the most part and have a great recipe to migrate the rest slowly over. I don't see a reason why you would want to start with a homegrown solution at any point in this process.
- InquisitiveMe 10y agoJust started learning salt stack for infrastructure provisioning. But it makes so much sense just to build all requirements in the container itself. Did anybody already moved from tools like salt/puppet to container only approach?