Hi,
I ran into a problem where I cannot ssh to containers but I could do
the reverse and ssh to the host from inside containers.
I'm doing this on ubuntu 12.04 and followed official tutorial. It
looks like it should be rather painless and I should be able to access
container through hostname or
Hi,
I ran into a problem where I cannot ssh to containers but I could do
the reverse and ssh to the host from inside containers.
I'm doing this on ubuntu 12.04 and followed official tutorial. It
looks like it should be rather painless and I should be able to access
container through hostname or
Hi,
I updated to lxc-0.8.0-rc2 and after that I observe dangling cgroups
(/cgroup/PID) in the filesystem after lxc-execute terminates.
I am using ns_cgroup.
Looks like a process is spawned in a new namespace but lxc-fails to remove
the cgroup directory.
After a long time these dangling cgroups
Hello Zeyang
I suggest doing a reverse DNS lookup from the host to check that the DNS
name of the container is what you think it is
dig +short -x 10.0.3.195
I have seen a situation (running LXC inside EC2 instances) where an
unexpected DNS name was being assigned to the guest by the wider
I remember reading post that says that in order to run lxc-execute, I
have to have lxc installed on the client.
On Fri, Jul 6, 2012 at 4:09 PM, Ben Butler-Cole b...@bridesmere.com wrote:
[back on-list]
On 6 July 2012 08:59, Li, Zeyang a.bankn...@gmail.com wrote:
I also see that you seem to
On Fri, Jul 6, 2012 at 5:50 PM, Li, Zeyang a.bankn...@gmail.com wrote:
I remember reading post that says that in order to run lxc-execute, I
have to have lxc installed on the client.
Do you use lxc-execute, or lxc-start? There's a BIG difference.
You don't need lxc on the guest for lxc-start
I recently ran across a similar situation where I could not access the
container behind a firewall.
This is how I got around that:
My host configuration:
##
@lxc3100:~# ifconfig
br0 Link encap:Ethernet HWaddr 00:26:18:81:1e:7d
inet
I recently ran across a similar situation where I could not access the
container behind a firewall.
This is how I got around that:
My host configuration:
##
@lxc3100:~# ifconfig
br0 Link encap:Ethernet HWaddr 00:26:18:81:1e:7d
inet
On 07/06/2012 04:09 AM, Ben Butler-Cole wrote:
[back on-list]
On 6 July 2012 08:59, Li, Zeyang a.bankn...@gmail.com
mailto:a.bankn...@gmail.com wrote:
I also see that you seem to be running the LXC network inside the
guest as well as on the host (it too has an lxcbr0 bridge
That fixed my problem. million thanks :D
Btw, is there a way to have lxc.init while not installing the full lxc
package? Is lxc.init the only thing I need in the container to have
lxc-execute working?
Zeyang
On Fri, Jul 6, 2012 at 9:48 PM, Stéphane Graber stgra...@ubuntu.com wrote:
On
Quoting Arun M (arunmahadevai...@gmail.com):
Hi,
I updated to lxc-0.8.0-rc2 and after that I observe dangling cgroups
(/cgroup/PID) in the filesystem after lxc-execute terminates.
I am using ns_cgroup.
Which kernel are you on? The ns cgroup is no longer available since
over a year ago.
Thanks, Sergem, This is already solved in another thread exatly as you
described. I accidentally started two threads. First time posting on
this list, sorry for the spam accident.
On Fri, Jul 6, 2012 at 11:01 PM, Serge Hallyn
serge.hal...@canonical.com wrote:
Quoting Li, Zeyang
On 07/06/2012 11:18 AM, Li, Zeyang wrote:
That fixed my problem. million thanks :D
Btw, is there a way to have lxc.init while not installing the full lxc
package? Is lxc.init the only thing I need in the container to have
lxc-execute working?
Zeyang
That's correct, you only need lxc-init.
I'm seeing a problem where I cannot lxc-stop or lxc-kill a container.
It happens rather sporadically, and there is nothing I could do other
than restart the host machine. Did anybody encounter this issue?
Thanks,
Zeyang
A continuation of my original question, after setting USE_BRIDGE to
false, I'm able ssh to the IP, but not the hostname. Not sure why
hostname is still not recognized.
Zeyang
On Fri, Jul 6, 2012 at 11:39 PM, Stéphane Graber stgra...@ubuntu.com wrote:
On 07/06/2012 11:18 AM, Li, Zeyang wrote:
Quoting Stéphane Graber (stgra...@ubuntu.com):
On 07/06/2012 11:18 AM, Li, Zeyang wrote:
That fixed my problem. million thanks :D
Btw, is there a way to have lxc.init while not installing the full lxc
package? Is lxc.init the only thing I need in the container to have
lxc-execute working?
On 07/06/2012 12:01 PM, Serge Hallyn wrote:
Quoting Stéphane Graber (stgra...@ubuntu.com):
On 07/06/2012 11:18 AM, Li, Zeyang wrote:
That fixed my problem. million thanks :D
Btw, is there a way to have lxc.init while not installing the full lxc
package? Is lxc.init the only thing I need in
On 6 July 2012 17:13, Stéphane Graber stgra...@ubuntu.com wrote:
- python3-lxc (arch: any, python module and python wrapper)
Should I understand that there are (or will be) Python bindings for lxc?
-Ben
--
Live
On 07/06/2012 12:42 PM, Ben Butler-Cole wrote:
On 6 July 2012 17:13, Stéphane Graber stgra...@ubuntu.com
mailto:stgra...@ubuntu.com wrote:
- python3-lxc (arch: any, python module and python wrapper)
Should I understand that there are (or will be) Python bindings for lxc?
-Ben
Quoting Ben Butler-Cole (b...@bridesmere.com):
I've been looking into this further and I think I've misunderstood how this
should work.
For some reason I thought that with the default lxcbr0 config the
containers name would resolve for it as a DNS name. That doesn't seem to be
the case.
20 matches
Mail list logo
