What's with:
# lxc-stop -n testlxc -k
?
--
With Best Regards,
Marat Khalili
On 27/09/16 05:46, John Y. wrote:
I create a container with lxc 2.0.4.
lxc-stop hangs up when I want to stop it.
#lxc-stop -n testlxc
But it may already stoped, because I exited from lxc auto
automatically and lxc
Hi,
I'm creating my lxd containers with ansible lxd_container module.
Working great. But once created, I need to execute a command inside the
container. Thought that I could simply type in my command as:
lxc exec mycontainer apt-get install -y puppet
You'll understand that this is a Ubuntu c
I create a container with lxc 2.0.4.
lxc-stop hangs up when I want to stop it.
#lxc-stop -n testlxc
But it may already stoped, because I exited from lxc auto automatically and
lxc-attach failed.:
#lxc-attach -n testlxc
lxc-attach: attach.c: lxc_attach_to_ns: 257 No such file or directory -
faile
On 2016-09-27 11:24, Mathias Gibbens wrote:
Hi,
Recently I've been setting up unprivileged LXC containers on an older
server that has 6GB of physical RAM. As my containers are running,
occasionally I am seeing OOM errors in the host's syslog when the
kernel
This system is running Debian
Hi,
Recently I've been setting up unprivileged LXC containers on an older
server that has 6GB of physical RAM. As my containers are running,
occasionally I am seeing OOM errors in the host's syslog when the kernel
kills a process within one of the containers. I did some investigation
and noticed
Lxc-create OK but this error at lxc-start:
lxc-start: utils.c: open_without_symlink: 1623 Too many levels of symbolic
links - init in /usr/lib/lxc/rootfs/sbin/init was a symbolic link!
I'm using lxc 2.04 on an embedded system ( NFS mounted for development ) with
init pointing to busybox. Is thi
Hi all,
I could have sworn in the past I was able to make an unprivileged
container use openvpn, but yesterday, i started an unprivileged
container and was not able to use openvpn because I did not have a
/dev/net/tun. I was able to get it started in a normal privileged
container after performing
# ls -ld /var/lib/lxd/containers/pld/rootfs
/var/lib/lxd/containers/pld/rootfs/var
/var/lib/lxd/containers/pld/rootfs/var/host
drwxr-xr-x 22 100 100 4096 Sep 26 12:33
/var/lib/lxd/containers/pld/rootfs
drwxr-xr-x 17 100 100 4096 Sep 26 10:05
/var/lib/lxd/containers/pld/rootfs/var
dr
On Mon, Sep 26, 2016 at 5:38 PM, Paweł A. Gajda wrote:
> I've added local dir (lxc config device add) to running (unprvileged,
> default profile) containter and it just works, but after container stop, it
> cannot start again with "Permission denied - Failed to mount". Any fix?
>
> $ lxc start pl
I've added local dir (lxc config device add) to running (unprvileged,
default profile) containter and it just works, but after container stop, it
cannot start again with "Permission denied - Failed to mount". Any fix?
$ lxc start pld
lxc 20160926115846.879 ERROR lxc_utils - utils.c:safe_mount:169
10 matches
Mail list logo