Docker support WIP (antidote is build in docker with the latest erlang)

[define-null]

Hi, I was curious about you jepsen tests for AntidoteDB and noticed that there is only support for lxc at the moment. I decided to have a look if I can easily integrate docker, with AntidoteDB that is build in the same base docker image, which is used in jepsen tests. I can see that in db.clj you expect antidote release to be present in _build/default/rel/antidote, however I couldn't find where do you clone and build it. It seems like some base makefile is missing, so I wonder if you can guide me how does your build step look like?

update: It seems like local paths are hard-corded in util.clj at the moment, maybe there is a good way to parametrize it, so that proper paths could be used in both docker and lxc?

[nurturenature]

Thanks for the comments!

As you noted, the documentation is incomplete, did a quick update, more to come.

Opened an issue, #38, to support specifying a local file, git, or a container, to install the db.

And as for Docker itself, the issue is Docker's lack of support/reliability for OS'ish containers (vs app or service) and Jepsen's use of system capabilities, privs, to inject faults.

I started out trying to get a full Docker system working, see:

• 6

• 13

Tried working with the Jepsen project:

• https://github.com/jepsen-io/jepsen/issues/532

And so on. Still thinking about alternatives...

P.S. apologies for the delay, and congratulations with AntidoteDB!

[define-null]

Interesting, I will be following your work in this direction :) Thanks for the update!

[nurturenature]

For the current state of Docker and systemd containers see Jepsen issue.

Current Docker updates do not support the ability to docker compose systemd containers on Linux and Windows and require a deprecated flag on macOS.

[nurturenature]

Thanks for your patience.

I ultimately did create a literal jepsen-docker-workaround to build/run AntidoteDB w/Jepsen.

Please ask if any questions or desired changes.