Hi, Thierry,
I think you don't understand how docker works when you build images and run containers.
You can't expect that you start a process when building a docker image and then it runs when you start a container based on the image.
During the build phase, if you want to configure the server using asadmin commands, you need to start the server and run asadmin commands against it.
But after the build phase, all processes are stopped as if the OS was shut down.
When you start a container, you need to indicate which processes to start. The default launch sequence given by the entry point and CMD command starts a single DAS.
You can launch additional asadmin commands if you pass a post-boot command file to the container. This file can even include asadmin commands to start other
preconfigured instances in existing deployment groups, or even can first create everything at boot and then launch the instances.
Ondro