Right now, both logging and runtime socket/pic files are kept in the same volume container, but separated by the dynamic $HOSTNAME variable. Using --net host makes that the same across all containers on the same host and therefore must be detected and changed accordingly so that multiple containers can use the option. Eventually, another method of inserting the unique container name will be used and we can resume normally with the scheme.
Right now, both logging and runtime socket/pic files are kept in the same volume container, but separated by the dynamic $HOSTNAME variable. Using
--net hostmakes that the same across all containers on the same host and therefore must be detected and changed accordingly so that multiple containers can use the option. Eventually, another method of inserting the unique container name will be used and we can resume normally with the scheme.