Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

themiddlewareman.org

Post reply on HN
Print view View original

11–20 of 58 posts

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#11

Post by tenfourty »

binocarlos wrote: post #10
tenfourty wrote: post #8

Earlier quoted context omitted.

I really hope so, with the work that Red Hat and dotCloud are doing it will be possible for a Docker container to run on any Linux OS - which is a significant first step towards ubiquity. Whether Heroku's Buildpacks are then able to be layered on top of a Docker container is the question, not impossible as they are open source but will Heroku come on board? It seems Red Hat's OpenShift is making the moves towards thi…

Jeff Lindsay wrote https://github.com/progrium/dokku which uses Heroku Buildpacks to build an app and then run it using Docker - it is a very neat little tool : )

Very true, this would be more compelling if Heroku got behind the project themselves because their build packs would be very portable and possibly a future standard. It seems that Docker is becoming the container of choice but how apps are layered on top is still very much up for debate.

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#12

Post by StavrosK »

alexlarsson wrote: post #6
StavrosK wrote: post #4

I would very much like to use Docker/containers to provision and deploy my software stacks on a beefy server I have. The ideal for me would be a whole VM in a container (nginx/uwsgi/redis/postgres/etc), but Docker can't currently do that (it only runs a single process). Is there a practical/good way to easily do what I want, with Docker or another tool?

The process docker runs in the container can be /sbin/init, which spawns an entire OS. Its just not how its normally used.

Hmm, I guess that could do it. I wonder if I can run the upstart daemon first to have it start my services. That would be ideal.

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#13

Post by StavrosK »

andreypopp wrote: post #9
StavrosK wrote: post #4

I would very much like to use Docker/containers to provision and deploy my software stacks on a beefy server I have. The ideal for me would be a whole VM in a container (nginx/uwsgi/redis/postgres/etc), but Docker can't currently do that (it only runs a single process). Is there a practical/good way to easily do what I want, with Docker or another tool?

Did you try Dokku[1] (git hook + Heroku buildpacks + Docker)? You can build/deploy several apps to docker containers using git push. It has PostgreSQL plugin and exposes your app via nginx. Of course it wouldn't be 100% usable as-is, but its codebase is very hackable — around 150LOC. For example I've forked it to built a μPaaS[2] — it has out-of-the-box integration with upstart (for supervision and logging) and repla…

The only reason I haven't tried it is because I've never really used Heroku, but I'll give it a shot now, thanks.

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#14

Post by steeve »

StavrosK wrote: post #4

I would very much like to use Docker/containers to provision and deploy my software stacks on a beefy server I have. The ideal for me would be a whole VM in a container (nginx/uwsgi/redis/postgres/etc), but Docker can't currently do that (it only runs a single process). Is there a practical/good way to easily do what I want, with Docker or another tool?

I actually spawn multiple processes thanks to supervisord, which also restarts them if needed.

See https://github.com/steeve/docker-lemp

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#15

Post by huxley »

StavrosK wrote: post #4

I would very much like to use Docker/containers to provision and deploy my software stacks on a beefy server I have. The ideal for me would be a whole VM in a container (nginx/uwsgi/redis/postgres/etc), but Docker can't currently do that (it only runs a single process). Is there a practical/good way to easily do what I want, with Docker or another tool?

This might be interesting too:

Pipework

https://github.com/jpetazzo/pipework

Essentially it lets you create private networks between containers which could each run its own service (one for Postgres, one for Redis, etc).

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#16

Post by StavrosK »

steeve wrote: post #14
StavrosK wrote: post #4

I would very much like to use Docker/containers to provision and deploy my software stacks on a beefy server I have. The ideal for me would be a whole VM in a container (nginx/uwsgi/redis/postgres/etc), but Docker can't currently do that (it only runs a single process). Is there a practical/good way to easily do what I want, with Docker or another tool?

I actually spawn multiple processes thanks to supervisord, which also restarts them if needed. See https://github.com/steeve/docker-lemp

That's my preference as well, I just prefer upstart to supervisord. Does anyone know how to start it offhand? It's probably just as easy as running the upstart daemon.

EDIT: Well, supervisord looks straightforward, and you only need a single config file for everything. You have swayed me, thank you for that. This will do perfectly, I will try it today.

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#17

Post by windexh8er »

StavrosK wrote: post #16
steeve wrote: post #14

Earlier quoted context omitted.

I actually spawn multiple processes thanks to supervisord, which also restarts them if needed. See https://github.com/steeve/docker-lemp

That's my preference as well, I just prefer upstart to supervisord. Does anyone know how to start it offhand? It's probably just as easy as running the upstart daemon. EDIT: Well, supervisord looks straightforward, and you only need a single config file for everything. You have swayed me, thank you for that. This will do perfectly, I will try it today.

There's a great example here of a well done Dockerfile and implementation using supervisor.

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#18

Post by windexh8er »

StavrosK wrote: post #16
steeve wrote: post #14

Earlier quoted context omitted.

I actually spawn multiple processes thanks to supervisord, which also restarts them if needed. See https://github.com/steeve/docker-lemp

That's my preference as well, I just prefer upstart to supervisord. Does anyone know how to start it offhand? It's probably just as easy as running the upstart daemon. EDIT: Well, supervisord looks straightforward, and you only need a single config file for everything. You have swayed me, thank you for that. This will do perfectly, I will try it today.

Can't edit on mobile, but here's the example referenced:

https://github.com/dotcloud/collectd-graphite?files=1

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#19

Post by jasonkolb »

StavrosK wrote: post #4

I would very much like to use Docker/containers to provision and deploy my software stacks on a beefy server I have. The ideal for me would be a whole VM in a container (nginx/uwsgi/redis/postgres/etc), but Docker can't currently do that (it only runs a single process). Is there a practical/good way to easily do what I want, with Docker or another tool?

Just create a bootstrap shell script that can be run on any machine. At a high level here's what mine does:

1) Install git 2) Clone a repo with all of the dockerfiles in it (each dockerfile corresponds to a container) 3) Install Docker 4) Start containers using the previously-mentioned scripts

The advantage to using a shell script for this is that you can start it manually or via an automated system. All you need is the bootstrap script and you can start your app on any machine. Well, apart from the distributions the post mentions I guess.

Re: Docker + Red Hat OpenShift = The Tipping Point for Open PaaS?

#20

Post by gabrtv »

Contrary to what you might think, those of us working on http://deis.io/ are excited by the Red Hat / Docker partnership and its implications on interoperability. Why? Because there will never be a one-size-fits-all PaaS.

Deis happens to be built around Chef with a workflow deeply inspired by Heroku. We believe strongly in that approach. Other PaaS's are working with more experimental technologies like CoreOS and etcd, others are going the Erlang route, others seem to be writing things from scratch in Go -- with all of it Docker compatible.

We think this is fantastic for the industry and for consumers (software teams) who will soon have lots of choices in open PaaS.

Post reply on HN