Hello!
Yes, sure! I'll investigate this question and update our doc.
On Thu, Dec 7, 2017 at 9:57 AM, Denis Magda <
[hidden email]> wrote:
> Nick,
>
> As one of Ignite docker maintainers, could you please investigate one how
> to map Ignite persistence to docker volumes:
>
https://docs.docker.com/engine/admin/volumes/volumes/#> use-a-read-only-volume
>
> and update the docker documentation:
>
https://apacheignite.readme.io/docs/docker-deployment>
> —
> Denis
>
> On Dec 1, 2017, at 8:40 AM, afedotov <
[hidden email]> wrote:
>
> Hi,
>
> You need to create volumes and map them to the ${IGNITE_HOME}/work/db or
> any
> other path that
> you might have specified via setPersistentStorePath. These volumes should
> outlive the Ignite containers
> and thus it will be possible to reuse them on restart.
>
> It's worth trying docker-compose, docker-swarm or kubernetes, depending on
> your needs.
> For example, Kubernetes provides a wide variety of volume options
>
https://kubernetes.io/docs/concepts/storage/volumes/>
>
> Has anyone use Ignite Native Persistence with Docker?
> Is there a solution on how to map the Volume dynamically? And how about
> when
> you restart the whole cluster, how does it maps all volumes?
>
>
> --
> Sent from:
http://apache-ignite-users.70518.x6.nabble.com/>
>
>
Locked
