Document in the wiki the name evolution

[gioppoluca]

You get some parameters like:
container name=webdk
image name= csi_webdk

We need to have documented how they are used and get changes in the evolution of the process
In the registry the image will become cloudopting/csi_webdk
the container name when compose do the up?
etc.

[gioppoluca]

ok so we need to add the container_name command in the docker-compose.yaml or the final container (and the hostname) will be wrong
From where does cloudopting_dbdk_1 comes out???
if we start from the following content?
dbdk:

image: cloudopting/csi_dbdk

why we loose csi_??

----Messaggio originale----

Da: jmcerpa notifications@github.com

Data: 03/02/2016 17.15

A: "CloudOpting/cloudopting-crane"cloudopting-crane@noreply.github.com

Cc: "Luca Gioppo"gioppoluca@libero.it

Ogg: Re: [cloudopting-crane] Document in the wiki the name evolution (#16)

image name ok, it's done.

registry image name ok, it's done.

container name... we have a problem: compose library for python impose the format prefix_service_numcontainer.

example: cloudopting_tomcatdk_1

           cloudopting_dbdk_1

           cloudopting_tomcatdk_2

Howerver, you can force the container name in docker-compose.yml with container_name: name.

example:

dbdk:

image: cloudopting/csi_dbdk

container_name: dbdk

Are you ok with this?

—
Reply to this email directly or view it on GitHub.

[jmcerpa]

Because compose not use the name of image, he use the name of service.
Example:

dbdk:
  image: cloudopting/csi_dbdk

the container name is cloudopting_dbdk_1

if you write:

csi_dbdk:
  image: cloudopting/csi_dbdk

The container name is cloudopting_csi_dbdk_1

service:
  image: image_name
  container_name: container_name

with container_name you choose the name. Otherwise, docker automatically choose the name and you do not have complete control.

but if you use container_name and the name already exists, then it does not work.
if you do not use it and the name already exists, then compose library gives cloudopting_csi_dbdk_2.

[jmcerpa]

What have you decided to do?