Kevin Centeno

> If there is no default user specified, create the lxdock user (password lxdock). We should also specify that the default user (whether `lxdock` or user-defined) is set for _password-less...

> But to me the whole point of LXDock is development containers, a lightweight alternative to Vagrant 💯

Another potential issue is how do we go about monitoring the guest-side Ansible output.

Ah, I agree that getting output from the guest is a high priority, regardless if it's from the Shell or _some other_ provisioner. Currently, it's a bit of a mystery...

With that said, does it make sense to have a default share set up, like how vagrant does with `/vagrant`?

I think the tie-in with a default `lxdock` user makes sense... but I think this user should be set regardless if a user or users are defined by the user....

A `default: yes` user option makes the most sense to me, especially because I alpha-sort my users; "first user is default" breaks this.

Is there a particular reason not to automatically set up a default share? Vagrant does this by default, and the user has to explicitly unset this default share: https://www.vagrantup.com/docs/synced-folders/ One...

That's fair. I prefer working out of the home directory of the vagrant user. I wonder if mounting in two places would break things?

I would say that this blocked by #133