We need to add configuration allowing us to specify the directory where the diagnostics server socket is created.
In scenarios where you may want to use a bind mount (e.g., containers) or symlink to share the directory in which the diagnostic server is created, it is unideal to have to share the entire /tmp directory.
#1600 attempted to solve this, but failed in the multi-process scenario since it required the fully-qualified path to the socket. Specifying the socket path failed since child processes inherited this configuration. By specifying just the directory, the conflict can be avoided avoided.
cc @josalem@wiktork@jander-msft
We need to add configuration allowing us to specify the directory where the diagnostics server socket is created.
In scenarios where you may want to use a bind mount (e.g., containers) or symlink to share the directory in which the diagnostic server is created, it is unideal to have to share the entire
/tmpdirectory.#1600 attempted to solve this, but failed in the multi-process scenario since it required the fully-qualified path to the socket. Specifying the socket path failed since child processes inherited this configuration. By specifying just the directory, the conflict can be avoided avoided.
cc @josalem@wiktork@jander-msft