This is a long awaited feature for us , since we are currently obliged to kill sensition daemon after warp10 docker launch and this not that easy.
We would like to have some "env var" (like 'WITHOUT_SENSITION" or "SKIP_SENSITION" or "DISABLE_SENSITION" as you prefer) that could be filled with "-e" docker run param , that will not run sensition daemon along warp10 instance.
The reason for this is the "huge" disk space consumed by sensition which we have currently no use in our process.
Hi,
This is a long awaited feature for us , since we are currently obliged to kill sensition daemon after warp10 docker launch and this not that easy.
We would like to have some "env var" (like 'WITHOUT_SENSITION" or "SKIP_SENSITION" or "DISABLE_SENSITION" as you prefer) that could be filled with "-e" docker run param , that will not run sensition daemon along warp10 instance.
The reason for this is the "huge" disk space consumed by sensition which we have currently no use in our process.