Page 4 of 4 FirstFirst ... 234
Results 31 to 31 of 31

Thread: LXD Based Container For Desktop Applications - Some Success - Help (need more)

  1. #31
    Join Date
    Aug 2005

    Talking Re: LXD Based Container For Desktop Applications - Some Success - Help (need more)

    Quote Originally Posted by TheFu View Post
    For complex dependencies, I understand why a container/VM would be useful. Same for applications that cannot be installed outside the default locations in an OS. That fits most webapp needs. Since I don't game or use WINE (anymore), the other examples don't mean much to me. It is easier to just keep 1 Win7 VM around for those Windows tools I haven't found replacements for, yet.
    I think you phrased it in a way that pushes the discussion forward. I listed the issues that were important and interesting to me.
    The way to discuss this, would be to get use-cases and describe which solution would be better suited.

    $ firejail --private /path/to/thunderbird
    is pretty easy. However, that isn't too useful with an email program - even with IMAP servers. I haven't played with any webapps and firejail. I'm a perl webapp dev. Shouldn't be too hard, since they all run in a self-contained area (including their own perl) and only use tcp connections between their cluster servers and the reverse proxy.

    Good discussion. Appreciated.
    Thunderbird would be OK for LXD as you get persistent storage.

    It would be more interesting to use LXD with webapps.
    You can deploy your app in all sort of Linux distributions, and automate the testing.
    While developing the webapp in a machine container, you can take a snapshots of the container.
    Then, you can continue developing and easily switch between snapshots of the container.
    See more at

    Quote Originally Posted by TheFu View Post
    BTW, you showed lxc, not lxd in the commands. Was that intentional?
    The LXC 1.0 commands have the form of "lxc-create", "lxc-attach" and so on. See more of them at
    However, in LXD there is the lxd executable that is the hypervisor (server), and the lxc executable that is the client. LXC 1.0 did not have a "lxc" executable, so LXD started using it for the client of these Linux containers.

    At you can see the differences between LXD and LXC 1.0 (they use the term "LXC").
    Last edited by DuckHook; January 16th, 2018 at 12:22 AM. Reason: Added missing [quote] tag

Page 4 of 4 FirstFirst ... 234


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts