Comment 5 for bug 1652424

I'll chime in that using `libertine-launch` is a convenient way to do these quick-and-dirty command line tasks, but we are content to let it continue to be "quick-and-dirty" because that is not its primary use case.

I wonder if we could get around all of this with some kind of new command called `libertine-shell $container_id` that would do all of the bind-mounts, etc, and launch a bash or ssh session inside the container. In that case, `libertine-shell` without an argument would use the default container.