Hi,
> Is there a reason for the difference?
The build process between ceph/ceph and ceph/{daemon,daemon-base} is different.
ceph/ceph container images are only built when:
- a new ceph release is available (like next 14.2.5)
- a new base image is available (like centos:7 update)
ceph/{daemon,daemon-base} container images are only built on ceph/ceph-container.git project changes.
> Should we be using ceph/ceph or ceph/daemon-base? What's the difference?
I think it depends on what you are looking for.
If you need stable images that follow the ceph releases then ceph/ceph is the way to go. Rook project is using them.
If you need devel images then ceph/{daemon,daemon-base} images is maybe more appropriate. As an example, you don't have octopus container images on ceph/ceph. Or if you want what is present in a stable branch but not released yet.
> It also seems to me "latest-" is unclear. Someone may think that
> "latest-nautilus" means the most recent release but it probably means
> (??) whatever ceph.git:heads/nautilus is. I'd recommend that be
> "dev-nautilus" instead. "nautilus" should be an alias for whatever the
> most recent release is.
Agreed it's unclear. The main confusion here is that it's not based on the ceph/ceph.git content but on ceph/ceph-container.git content.
So latest-nautilus container tag doesn't mean the latest ceph nautilus content but the latest build system based on nautilus.
Worth to mention it but the latest-xxxx tags are based on the stable ceph release from
download.ceph.com except the master one based on chacra bits.
That's why you can't have latest ceph/ceph content from a stable branch with latest-xxxx tag.
> Hmm, also, what's the difference between latest-master and latest-master-devel?
Because the latest-xxxx are based on the stable ceph release (except master) some people would like to test the unreleased code on a stable branch.
That's why there's the latest-xxxx-devel tag. The ceph bits come from chacra and we're using a nightly job to build the container image.
Regards,
Dimitri