Local Docker Setup
Guide into using Antidote's Docker images.
For easy installation and deployment, we recommend to use Antidote's Docker images.
The hub repository provides images for Antidote releases (currently 0.2.1 / 0.1.1).
The AntidoteDB images come in many flavors, each designed for a specific use case.
antidotedb:latest: the most recent AntidoteDB version (unstable).
antidotedb:stable: the most recent stable official release (recommended).
antidotedb:alpine: the most recent lightweight alpine release (stable).
antidotedb:<release>: Docker image for a specific version of AntidoteDB
antidotedb:<release>-alpine: This variant, available for each official release, is recommended when final image size being as small as possible is desired. The main caveat to note is that it use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libs requirements. However, most software does not have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
Supported tags and respective
Start a local node with the command
This should fetch the Antidote image automatically. For updating to the latest version use the command
docker pull antidotedb/antidote:stable.
For building the Docker image on your local machine
Then you can run it using:
To remove the local Docker image, you can use:
Antidote should now be running on port 8087 on localhost.
You can connect to the console of a local node typing the following:
docker exec -it antidote1 /antidote/bin/antidote remote_console