Just for information , I am now able to run google-chrome also. Now only
thing left is to understand what the heck xhost does :D .
Thanks.
On Sun, Aug 10, 2014 at 11:11 AM, Veer Singh wrote:
> When I execute "xhost +" in host (arch linux) , I am now able to
> successfully to run firefox in co
hi kevin,
lxc on ubuntu 14.04 works awesome straight out of the box. Only for
unprivileged container you have to add a single config file in
~/.config/lxc/default.conf, and rest everything works awesome. I am running
it for various use cases now, i generally use it along side chef (to
control the h
When I execute "xhost +" in host (arch linux) , I am now able to
successfully to run firefox in container and can use its gui window on host
. I think error that I was getting might have to do with some permissions
on who can use display . I wonder how to set this permission and what
exactly to se
lxc-users@lists.linuxcontainers.org
Hello ,
I am running a unprivileged container (as shown here :
https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/ ) in host
Arch Linux (amd64) and template is precise-gui (amd64 version) downloaded
as given in above link.
I am able to run this un
Does anyone know of a good blog post or other such document that steps some one
through the entire set up process for LXC 1.0 and Ubuntu 14.04?
Over a year ago I did some test with 12.04 and LXC 0.6 and while it worked for
those test, it was the best kludge, I think I ever did.
I wiped that t
On Sat, 2014-08-09 at 11:02 -0400, CDR wrote:
> That is correct, but why not a command called "lxc-cancelautostart"?
Unnecessary.
> It seems obvious.
Not really. Not other solutions exist.
Regards,
Mike
> On Sat, Aug 9, 2014 at 10:57 AM, Tom Weber
> wrote:
> > Everything is there already. Ev
Third solution proposal near bottom. Sorry for longish post, but...
On Sat, 2014-08-09 at 10:32 -0400, CDR wrote:
> This is a philosophical divide. I live in the real world, and are
> successfully moving all my business to LXC, or a combination of LXC
> and real virtualization, where you have a
because everything you need is already there.. you request a feature
noone needs and that you can implement yourself already...
another approach:
man lxc.container.conf(5)
see lxc.hook.pre-start
make that script check for /tmp/lxcdontautostart and bail out if it
exists.
Tom
Am Samstag, den
That is correct, but why not a command called "lxc-cancelautostart"?
It seems obvious.
On Sat, Aug 9, 2014 at 10:57 AM, Tom Weber
wrote:
> Everything is there already. Even in real world.
> you could:
> - define a run level for this purpose
> - delay the autostart
> - run your own script during
Everything is there already. Even in real world.
you could:
- define a run level for this purpose
- delay the autostart
- run your own script during bootup which asks you wether it should kick
off the lxc-autostart process or not - it might default to yes after a
timeout if no input occurs
- create
This is a philosophical divide. I live in the real world, and are
successfully moving all my business to LXC, or a combination of LXC
and real virtualization, where you have a few virtual machines with
hundreds of GBs of RAM and 36 or more cores, and these super-virtual
machines act solely as cont
On Sat, 2014-08-09 at 09:26 -0400, Michael H. Warfield wrote:
> On Sat, 2014-08-09 at 02:39 -0400, CDR wrote:
> > make rpm fails.
> Point of order... Things like this should be reported to the lxc-devel
> list. This is not a "user" issue but a "development" issue.
Ignore the above remark. Now
On Sat, 2014-08-09 at 02:39 -0400, CDR wrote:
> make rpm fails.
Point of order... Things like this should be reported to the lxc-devel
list. This is not a "user" issue but a "development" issue.
Looks like a patch Martin Pitt submitted back on July 31 missed adding
lxc.net to lxc.spec.in. His
I've been reading this thread and this is the first *and only time* I've
ever heard anyone request such a "kill all" command for LXC to terminate
auto-start.
Developer time is always in short supply and IMHO asking one of them to
spend their time on such a *"corner-case" issue* is not putting thei
14 matches
Mail list logo
