Hello
I find that I can't do a read-write bind mount within a container (that is
to say, the source and target for the mount are both within the container's
own filesystem). I believe that it is being restricted to read-only by
Apparmour.
I understand that there are security reasons for denying
On 5 January 2013 12:29, Alan McDuff alan.mcd...@yahoo.com wrote:
If you paste the .lxc part from
http://www.stgraber.org/2012/07/17/easily-ssh-to-your-containers-and-vms-on-ubuntu-12-04-lts/
into
your ~/.ssh/config and start the container, then you should be able to ssh
with ssh
I'm using a very similar setup to this in production now, without any
problems.
It's not clear from your description how you are planning to do the port
forwarding to the reverse proxy. We are using iptables for this.
-Ben
On 4 January 2013 19:52, James Gallagher ja...@jamesgallagher.ie wrote:
On 4 September 2012 13:11, Matthew Franz mdfr...@gmail.com wrote:
Without sparking a golden image vs. os template debate, you would be better
off using a something like Chef/Puppet/SaltStack to drive those different
application server roles than hardcoding them in the template.
I agree with
On 6 July 2012 19:56, Serge Hallyn serge.hal...@canonical.com wrote:
Quoting Ben Butler-Cole (b...@bridesmere.com):
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.
Do you have 10.0.3.1
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
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 28 June 2012 23:11, Serge Hallyn serge.hal...@canonical.com wrote:
Quoting Ben Butler-Cole (b...@bridesmere.com):
However the default dnsmasq configuration, combined with the way EC2's
DNS
servers behave, means that my containers are getting EC2-like DNS names
assigned automatically
Hello
I'm using LXC on EC2, with Ubuntu host and guests. Currently using 11.10
and now upgrading to 12.04. The new functionality to set up the bridge
network automatically is great and should make my life a lot easier.
However the default dnsmasq configuration, combined with the way EC2's DNS
On 8 May 2012 10:13, Đỗ Hoàng Khiêm dohoangkh...@gmail.com wrote:
Suppose that I want to build a system to serve many app. execution
requests from outside, and I want each app will have an isolated
environment to run, so each time process an execution request I have to
create a container for
10 matches
Mail list logo
