Add necessary things for rgw in base or build a new one for rgw only? about ceph-container

[leseb]

@Ulexus Can you test this? https://registry.hub.docker.com/u/ceph/base-rgw/ with #18

[Ulexus]

@leseb There's no need for another base, since apache et al are installed specifically for the purpose of radosgw and are not really a reusable component. Just put the apache installation (apt-get install ...) into the radosgw Dockerfile. (I don't see the base-rgw on the Github side, so I can't see what's in it)

Also, I don't think you should have to run with --net=host. The issue with the MON and OSD containers and --net=host (if I recall correctly) is that ceph is really picky about the IP addresses. radosgw isn't much more than a client proxy, as I understand it, so it shouldn't matter if it runs on a different IP... is that assumption correct?

[leseb]

Ok I'll simply re-use base and install the necessary component for radosgw.
Correct the issue is with the MONs where they can't work behind a NAT.
Ending up with these kind of messages:

.connect claims to be [::1]:6804/1031425 not [::1]:6804/31537 - wrong node!

[Ulexus]

base: Yeah, that's exactly what I was meaning

nat: Okay, that makes sense. --net=host it is.

[Ulexus]

Oh... I see. Yeah, you're installing all the stuff at runtime instead of buildtime. Put all the installation in the Dockerfile, not the execution script.

[leseb]

Ack.

[Ulexus]

Also, you'll probably want to run apache directly (or with supervised or similar) rather than the default Debian init scripts. You don't want to run the whole init system for just Apache and radosgw

[leseb]

Ok will run apache from the cli, not really familiar with supervised.
Pushing a version in a couple of minutes.

[Ulexus]

Sorry, misnamed it: supervisord

I've never actually used it myself, as I try to avoid containers running multiple daemons. In this case, though, it doesn't really make sense to split up apache and radosgw. Many people in the Docker world use it. monit is also reasonably common, and I have used it.

In either case, the idea is that the execution blocks on a single command. Otherwise, you have to run one process in the background, and if it dies, you (and Docker) won't know about it. Hence, you want to use some sort of light-weight process manager when running multiple daemons inside a Docker container.

[Ulexus]

I should also mention that monit has the advantage of being in the Debian (and Ubuntu) package system already, so it is just an apt-get away.

[Ulexus]

Also, I'll have some time next week to tidy it up (wrap it in a monitor, rearrange build options, etc) if you want to push what you've got over the weekend.

[leseb]

Great thanks :)

[Ulexus]

Merged

[Ulexus]

I just wrapped the radosgw in a monitor, and the build is up on Docker Hub, so I think we're done, here.