All of
 help / color / mirror / Atom feed
From: kefu chai <>
To: Nathan Cutler <>
Cc: Mingliang LIU <>,
	"" <>
Subject: Re: Building Ceph in Docker
Date: Tue, 29 Aug 2017 21:53:02 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Aug 29, 2017 at 6:27 PM, Nathan Cutler <> wrote:
>> I know we're building Ceph in Linux distributions and many of you use
>> as I do. Steps to install dependencies are easy so we don't
>> have to worry about prerequisites in a dev machine.
>> I'm thinking if it's useful to build Ceph in Docker. There are reasons
>> to do this, for example 1) not be able/willing to install quite a few
>> dependency software/library on a shared Linux, 2) to have a standard
>> build image for isolated and automatic testing, and 3) to build on
>> Mac/Windows. I know for this we can create Linux virtual machines on
>> Mac/ Windows, but I think container is lightweight and better.
>> So I attach a small script that creates a Docker image to build the
>> Ceph from source, and then starts a test cluster with in a
>> container. Do you think it's something useful and/or worth to have in
>> source tree?
>> When I was building Hadoop, I found its helpful,
>> which is basically the same idea I borrowed here.
> Have you looked at ?
> I have not tried it in awhile, but it used to be able to not only build Ceph
> but also run "make check", in a Docker container. It support(ed) several
> different operating systems.
> It would be nice if someone got it working again.

it still worked the last time i tried to build luminous on
debian/stretch. (i hacked src/test/debian-jessie a little bit).

> Nathan
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to
> More majordomo info at

Kefu Chai

      reply	other threads:[~2017-08-29 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  6:06 Building Ceph in Docker Mingliang LIU
2017-08-29 10:27 ` Nathan Cutler
2017-08-29 13:53   ` kefu chai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.