Richard Lupton

@bossmc - will probably get started on this tomorrow, but this is roughly what I'm thinking.

I was thinking of backing it with a host path, creating it as needed. It can be overiden later, or we could provide some kind of merge strategy (but that...

@bossmc on the linked PR I have some basic volume support (the first tick box above). It's not quite polished yet - it creates folders with the user permissions (not...

Actually, I'm not sure if in general we'd want things automatically mounted into `dind`. I might opt to make it configurable (having just done the refactoring required to make it...

(My initial testing has successfully bound a rust registry - no rebuilds when relaunching the container!)

Cool. I think I'm happy with what I have as a first chunk of work, so after a review and a bit more testing I'll probably get it merged.

I just merged #36 , so that gives the core volume support.

I think the next step I want to take here is to add a simple subcommand to list out the volumes and their backing paths. This ought to make tracking...

It's unclear if this is actually always desirable.