Thanks for the explanation. It helps me understand why that path does not
exist. I added 'jenkins' to the root group, and then chmod'd 775 on /.
Unfortunately, this doesn't work either. When I do this, I suspect the
workspace is being mounted at /, which breaks all the things (specifically,
the
Is it possible to use absolute paths for the workspace at the time the
docker container is being created/run with declarative pipeline? I have
done this before with mesos docker cloud, but I am hoping to replicate that
ability locally, without having a mesos cluster on my localhost.
An example
