Skip to content
This repository has been archived by the owner on Apr 8, 2024. It is now read-only.

Commit

Permalink
Add --env CRATE_HEAP_SIZE=1g to docker run examples.
Browse files Browse the repository at this point in the history
  • Loading branch information
surister committed Jan 18, 2024
1 parent e768fb3 commit a0285f0
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 9 deletions.
2 changes: 1 addition & 1 deletion docs/basic/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,7 @@ horizontally scalable architecture that lends itself well to containerization.
In order to spin up a container using the most recent stable version of the
official `CrateDB Docker image`_, use::

docker run --publish=4200:4200 --publish=5432:5432 --pull=always crate
docker run --publish=4200:4200 --publish=5432:5432 --env CRATE_HEAP_SIZE=1g --pull=always crate

.. TIP::

Expand Down
16 changes: 8 additions & 8 deletions docs/containers/docker.rst
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ You can then create your first CrateDB container and node, like this::
--name=crate01 \
--net=crate \
-p 4201:4200 \
--env CRATE_HEAP_SIZE=2g \
--env CRATE_HEAP_SIZE=1g \
crate -Cnetwork.host=_site_ \
-Cnode.name=crate01 \
-Cdiscovery.seed_hosts=crate02,crate03 \
Expand Down Expand Up @@ -148,7 +148,7 @@ Now add the second node, ``crate02``, to the cluster::
--name=crate02 \
--net=crate \
-p 4202:4200 \
--env CRATE_HEAP_SIZE=2g \
--env CRATE_HEAP_SIZE=1g \
crate -Cnetwork.host=_site_ \
-Cnode.name=crate02 \
-Cdiscovery.seed_hosts=crate01,crate03 \
Expand All @@ -175,7 +175,7 @@ You can now add ``crate03`` like this::
sh$ docker run --rm -d \
--name=crate03 \
--net=crate -p 4203:4200 \
--env CRATE_HEAP_SIZE=2g \
--env CRATE_HEAP_SIZE=1g \
crate -Cnetwork.host=_site_ \
-Cnode.name=crate03 \
-Cdiscovery.seed_hosts=crate01,crate02 \
Expand Down Expand Up @@ -217,7 +217,7 @@ can be bypassed by passing the ``-Cnode.store.allow_mmap=false`` option to
the ``crate`` command::

sh$ docker run -d --name=crate01 \
--net=crate -p 4201:4200 --env CRATE_HEAP_SIZE=2g \
--net=crate -p 4201:4200 --env CRATE_HEAP_SIZE=1g \
crate -Cnetwork.host=_site_ \
-Cnode.store.allow_mmap=false

Expand All @@ -230,7 +230,7 @@ You can also start a single node without any bootstrap checks by passing the

sh$ docker run -d --name=crate01 \
--net=crate -p 4201:4200 \
--env CRATE_HEAP_SIZE=2g \
--env CRATE_HEAP_SIZE=1g \
crate -Cnetwork.host=_site_ \
-Cdiscovery.type=single-node

Expand Down Expand Up @@ -377,7 +377,7 @@ per host machine.
If you are running one container per machine, you can map the container ports
to the host ports so that the host acts like a native installation. For example::

$ docker run -d -p 4200:4200 -p 4300:4300 -p 5432:5432 crate \
$ docker run -d -p 4200:4200 -p 4300:4300 -p 5432:5432 --env CRATE_HEAP_SIZE=1g crate \
crate -Cnetwork.host=_site_


Expand All @@ -389,7 +389,7 @@ and go, and any data inside them is lost when the container is removed. For
this reason, you should mount a persistent ``data`` directory on your host
machine to the ``/data`` directory inside the container::

$ docker run -d -v /srv/crate/data:/data crate \
$ docker run -d -v /srv/crate/data:/data --env CRATE_HEAP_SIZE=1g crate \
crate -Cnetwork.host=_site_

Here, ``/srv/crate/data`` is an example path, and should be replaced with the
Expand All @@ -409,7 +409,7 @@ removed.
Here is an example of how you could mount the ``crate.yml`` config file::

$ docker run -d \
-v /srv/crate/config/crate.yml:/crate/config/crate.yml crate \
-v /srv/crate/config/crate.yml:/crate/config/crate.yml --env CRATE_HEAP_SIZE=1g crate \
crate -Cnetwork.host=_site_

Here, ``/srv/crate/config/crate.yml`` is an example path, and should be
Expand Down

0 comments on commit a0285f0

Please sign in to comment.