(Migrated) About Zato in Docker container

(This message has been automatically imported from the retired mailing list)

Hello, I’m trying to get a docker container with Centos and Zato using a
rpm package of zato…
First I found that the rpm package Dariusz give me to test wasn’t updating
the PATH variable… I update it
now I have some problems and workarounds of how to use it into docker
containers:

  • if Redis(kvdb) and Postgresql(odb) are into docker containers and you
    will use docker links to connect the containers… you will need to use
    hostnames and skydns or other service to detect the internat ip address of
    the other containers
  • a problem I can’t solve yet is that the zato’s quickstart always ask
    (interactively) for odb’s and kvdb 's user password even if I add it to the
    stored config file… and it can’t be empty via the command line

any other idea of how to do it?

Hi Anielkis,

We also have developed a container for Zato.

Instead of zato quickstart, we run the commands that quickstart runs
ourselves.

We do this from a Makefile that is executed subsequent to the docker
image being built.

The reason we do not put the result of the zato commands in the docker
image is that they depend on configuration details, for example, the
database connection details. We use one docker image for all our
environments (dev, test, staging, prod)… so we don’t put config
details like that in the image. Hope that makes sense :slight_smile:

These are the commands that our makefile runs, replacing quickstart

mkdir -p [path to deploy]
zato ca create ca
zato create odb
zato create cluster
zato ca create server
mkdir -p [path to server]
zato create server
zato start
zato enmasse

… perhaps we can give you a copy of our Dockerfile and Makefile…
I’ll take a look to see if there’s anything sensitive in there.

But on your password problem, on the master branch of zatosource/zato ,
commit dd1eef630470c47185e46d26549768d560bacf72 made it possible to do
say --odb_password “”, and provide a blank password. Works for
–kvdb_password too.

So if you pull the latest from the master branch you should be ok.

Cheers,
Alex

On 03/03/14 10:03, Anielkis Herrera wrote:

Hello, I’m trying to get a docker container with Centos and Zato using
a rpm package of zato…
First I found that the rpm package Dariusz give me to test wasn’t
updating the PATH variable… I update it
now I have some problems and workarounds of how to use it into docker
containers:

  • if Redis(kvdb) and Postgresql(odb) are into docker containers and
    you will use docker links to connect the containers… you will need to
    use hostnames and skydns or other service to detect the internat ip
    address of the other containers
  • a problem I can’t solve yet is that the zato’s quickstart always ask
    (interactively) for odb’s and kvdb 's user password even if I add it
    to the stored config file… and it can’t be empty via the command line

any other idea of how to do it?