We are running an image via compose without any problems so far. We use network definitions, volumes and port mappings so that the application is accessible from the out-site. Now we’d need to run the same image a second time on the same host - however binding to a different IP, using different volumes and networks.
Therefore we copied the .yml files and changed all names except the name of the image (which is the same) i.e. container-name, hostname, network, volume, port.mappings to avoid any conflicts. However as soon as we start the second compose file the container gets recreated and the first container stops. Any change to get the same image running twice on the same host with different configuration parameters?
1 Like
Same issue here with wildfly images.