Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using lxc or lib-container instead of Docker #3

Open
stuartpb opened this issue Aug 26, 2014 · 1 comment
Open

Using lxc or lib-container instead of Docker #3

stuartpb opened this issue Aug 26, 2014 · 1 comment

Comments

@stuartpb
Copy link
Member

It feels like we're fighting against Docker's features as frequently as we're using them. What we use Docker for:

  • Giving each app its own network stack
  • Isolating apps from the host system
  • buildstep
  • logging (badly)
  • Having a root-equivalent user to run Nginx with

Basically it feels like the bulk of what Docker is built to offer is largely a hypervisor for the meta-structure we're already tracking in $PLUSHU_ROOT. I feel like we could make a better system by rolling something better fitting out of some combination of lxc and/or libcontainer, systemd, and iptables directly.

On the other hand, this works right now, having prebuilt Docker images is kind of nice for addons/services, and it's something that has a lot of external appeal. I don't know that the advantages in reducing overhead by removing Docker would be so great.

@stuartpb
Copy link
Member Author

stuartpb commented Dec 9, 2014

So, there are definitely at least two things here where Docker is a good solution, for Nginx and addons.

However, Docker's image/link model isn't so great for building/running apps. What I'd really like is a system that lets me do copy-on-write layers and cgroup functionality, but without having to reify a ton of images.

This might also help with seamless failover?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant