Richard Lupton

Seems pretty reasonable. The dind container runs with privileged, and I think in general this should be fine for reproducibility. I'll have a quick look over the docker Docs to...

Just taking a look into this at the moment. I'm trying to understand what's really needed here. In general `floki` tries to avoid anything which makes the container environment reflect...

@mviereck thanks - yeah, I think the precise permissions need to be understood. This refers to mounting of loopback block devices (`/dev/loop0` etc) from the host device. Essentially the game...

@bossmc fyi. I will change the interface a bit, but this is a first small step on providing better volume ergonomics.

I think with respect to user facing documentation we should strive to document the YAML format that people actually use. Certainly we're nowhere near that at the moment. Some basic...

@bossmc sounds like a reasonable idea.

#19 adds an environment variable which contains the host working directory (`FLOKI_HOST_WORKDIR`), since that seems to be the absolute minimum needed (I think bind mounts would unlock the rest, in...

Actually, simpler than bind mounts, a symlink might do it. ``` init: - mkdir -p $(dirname $FLOKI_HOST_WORKDIR) - ln -s $FLOKI_HOST_WORKDIR link - cd link ```

@bossmc don't know why I've been sitting on the idea of mirroring the host path as an option for so long. It just occurred to me today it makes enough...

Currently proposing a new YAML field as below: ``` volumes: key: # only used if the volume is shared, otherwise, just a useful piece of documentation shared: false # optional,...