One of my containers is shutting down seemingly randomly. I'm trying
to figure out why, but so far all I can find in syslog is systemd[1]:
Received SIGRTMIN+3. which seems to be related to the LXC/LXD stop
command, but I can't find anything that might be sending that command
from my host, so I'm he
19wolf@Nephele:~$ lxc list
>Permission denied, are you in the lxd group?
19wolf@Nephele:~$ sudo adduser 19wolf lxd
>The user `19wolf' is already a member of `lxd'.
19wolf@Nephele:~$ lxc list
>Permission denied, are you in the lxd group?
What do I do? 'sudo lxc list' works fine
That's is what I've also been trying to do
Kubernetes has a list of supported persistent volume types, of which the
only one's that aren't cloud-based that I've tried are NFS, CephFS,
Glusterfs, and HostPath
https://kubernetes.io/docs/user-guide/persistent-volumes/#types-of-persistent-volumes
Wi
Adam Richter writes:
> Hello, Eric.
>
> Thank you for your prompt response to my posting.
>
> If you think that the new lxc behavior is acceptable, I am OK with it
> too. I just wanted to let you know because I thought that there was
> perhaps a ~30% chance that you might s
"Serge E. Hallyn" writes:
> Quoting Eric W. Biederman (ebied...@xmission.com):
>> Adam Richter writes:
>>
>> > On Linux 4.8-rc1 through 4-8-rc6 (latest rc), lxc fails start to
>> > Ubuntu 16.04 and Centos 7 containers [1], unless I first run
>
t; possible denial of service attack. Reversing the commit also restores
> successful commit the need to run that cgmanager process. [Eric and
> Tejun, I have bcc'ed you so you can be aware of this discussion
> thread, as you apparently respectively wrote and approved the commit
On September 8, 2016 2:53:38 PM EDT, Claudio Corsi wrote:
>I tried a number of scenario, including restarting the container after
>adding the device to it.
>
Sometimes the container needs to be fully stopped, and started again for the
changes to take in effect
___
On Thu, Sep 8, 2016, 01:05 Claudio Corsi wrote:
> Hello,
>
> I am attempting to get a Linksys AE3000 USB wireless dongle to work within
> my container. I am running LXC 2.0 on Ubuntu 16.04 and have an Ubuntu 16.04
> guest up and running.
>
> In both the host OS and the container the device is det
On Thu, Sep 8, 2016, 01:05 Zach Lanich wrote:
Umberto, I’m not 100% sure of what SaltStack uses under the hood lib wise,
but it’s written in Python an already does everything that Lib does. We’re
talking more of how the creation of the LXD containers themselves,
including setting Mounts, Static IP
On August 14, 2016 9:55:36 AM EDT, Personal wrote:
>I would have to at very least chown the subdirectory to the same user
>the container is running on in order to have write access to it from
>with in the container, but that was my thought that the volume itself
>provides enough protection. My fri
On July 31, 2016 4:22:28 PM EDT, Simos Xenitellis
wrote:
>Hi All,
>
>I have written a few articles on LXD containers and here is the latest,
>https://simos.info/blog/how-to-set-up-multiple-secure-ssltls-qualys-ssl-labs-a-websites-using-lxd-containers/
>
>It's about putting websites in different
Is there a way to mount an ecryptfs directory within a LXD/LXC container?
All I've tried so far is:
Editing, and reloading, /etc/apparmor.d/lxc/lxc-default [1][2]
|mount options=(rw, bind), ||mount fstype=(ecryptfs), |
After reloading apparmor I still get this error message:
|Exiting. Unable t
s
in the right way it stops being dumpable. Currently dumpable is a very
simple global thing, not a user namespace isolated thing.
We have talked about sorting this out but it has never been on the top
of anyone's list to do.
To make this work I think we need dumpable to change to an indicat
.
do you have any idea which option should be enabled in order to get a dhcp
ip from the lxc0 bridge?
it would make sense to extend the lxc-checkconfig misc option with these
kernel configuration
I attach the kernel config
Best Regards
--
Eric Keller
mailto: eric.keller@roche.com
www.roche.ch
-downloaded-key
Hope this helps
Regards
Eric
On Dec 13, 2014 7:21 PM, "Thouraya TH" wrote:
> Hello, Please i have already posted this question but i haven't any answer;
> i found this solution on the web:
> http://askubuntu.com/questions/544597/lxc-create-hangs-and-fina
> It looks like access permissions are the main issue.
>
> Yeah, looking at the file on the host it is root-owned, and not
> world readable.
>
> Each unpriv container gets its own l2 stack, but I'm not sure whether
> the list of ip tables is also different per container.
apparmor lxc-default profile. Currently disabling apparmor when
configuring locales in the container, and re-enabling apparmor afterwards
Cheers
--
Eric Keller
On Sat, Nov 8, 2014 at 8:53 AM, Eric Keller wrote:
> Hi everyone,
>
> I am currently using LXC (debian wheezy) container on my Ubu
Hi Neil,
thanks for the answer, there is no such package (language-pack-en-base) in
debian repositories :(
Regards,
--
Eric Keller
On Sat, Nov 8, 2014 at 9:01 AM, Neil Greenwood
wrote:
> On 8 Nov 2014 07:54, "Eric Keller" wrote:
> >
> > Hi everyone,
> &g
has someone a hint where I could investigate
N.B.: /etc/default/locale /etc/locale.gen and /etc/profile are set
according to the debian wiki page
here are the deailed setup steps executed in the container as root:
apt-get purge locales-all
dpkg-reconfigure
Guillaume Thouvenin writes:
>
> Hello,
>
> I have a card with two nvidia GPUs. Currently I'm using it in one
> LXC. I compiled the nvidia drivers from their our official web site in
> the container. I created /dev/nvidia0, /dev/nvidia1 and /dev/nvidiactl
> devices into the container. From
20 matches
Mail list logo
