Re: [lxc-users] Setting PATH environment variable, or installing golang in a container

2016-09-20 Thread Scott Lopez
This is more a shell question than anything particular to LXD. Just prepend the variable you want to the beginning of your command: GOPATH=/some/path/here apt install some_software for something more permanent, edit the default path variable IN the container, probably /etc/login.defs - you

[lxc-users] Setting PATH environment variable, or installing golang in a container

2016-09-20 Thread Matt Green
Hi, I'm trying to install golang in a container, I can push an "apt install" command to make that work, but then when I try and run stuff I get an error about environment variables "$GOPATH not set". It looks like there's some support for setting them in LXD, but I can't work out how to do it,

[lxc-users] not able to read-write to eeprom inside lxc container

2016-09-20 Thread manik sheeri
Hi, I am using lxc container. and I have an eeprom on my hardware board connected via i2c adaptor. my gaming application uses this eeprom to store some settings. In my sysfs, the eeprom nodes are: /sys/devices/platform/ocores-i2c.0/i2c-23/23-0054/eeprom

Re: [lxc-users] LAN for LXD containers (with multiple LXD servers)?

2016-09-20 Thread brian mullan
Serge, > > > > *> Automatically builds tunnels through firewalls and NATs without any > further> setup (for example, port forwarding).I would not appreciate > something which "automatically" (whatever itmeans) traverse my firewalls, > to be honest. We should treat our dataseriously, Brian.*

Re: [lxc-users] lxc 2.0.4 lxc-ls show nothing and lxc-attach fail

2016-09-20 Thread Fajar A. Nugraha
On Tue, Sep 20, 2016 at 8:06 AM, John Y. wrote: > I run a container as: > lxc-start -n test2 -f /root/test.cfg > > I can get info by lxc-info > #lxc-info -n test2 > Name: test2 > State: RUNNING > PID:15615 > CPU use:1.62 seconds >

Re: [lxc-users] lxc-ls show containers which does not exist with lxc 1.0.6

2016-09-20 Thread Fajar A. Nugraha
On Tue, Sep 20, 2016 at 10:51 AM, John Y. wrote: > before craete a container: > > #lxc-ls > show nothing > > 1. Why there are some lxc still in lxc-ls when I use `lxc-stop -n test2 > -k` (or use `kill -9 pid`) to stop it?2. How to remove these unused lxc > info? > >