Anders
Anders
> Do you have any release plans? Nothing formal, no. Until now, tagged versions have been on an ad-hoc basis when people needed them. > do you think that master...
> I got a little bit confused about this... Because this issue was opened by Marcin himself. I... what? Oh... man, I read that issue way too quickly. Haha! OK,...
@myhro, sure - go right ahead :-) At some point I also need to make a new version for pypi. It's quite outdated :-(
I think you actually managed to interrupt it _during_ the mounting process, meaning bootstrap-vz hasn't had the chance to flag the mount as completed, which in turn causes it to...
Oh! I see what you mean now (reopening). Hm, so the problem is we manage the state of a mount separately from what is actually happening on the system, which...
Makes a lot of sense, this should definitely be supported. As a workaround until this is implemented you should be able to use `--catenate` to append a Vagrantfile to the...
Woops, forgot the `tar` part. Yes, exactly.
> [..] and should be mitigated by not mounting /dev, /dev/pts, /proc and /sys from the host (but instead creating independent instances). [We only mount-bind `/dev`](https://github.com/andsens/bootstrap-vz/blob/151dcf5a85f77c96a7439497b8f75e65461a6305/bootstrapvz/common/tasks/filesystem.py#L110). When looking through the...
> Any tasks/workarounds/etc. created to specifically support this release should be removed from the code base and documentation. Agreed. Though we should tag the commit before that, just so people...
Yup, that's fine. Go right ahead.