On Sat, Jan 03, 2015 at 09:55:53PM +0100, Thouraya TH wrote:
> i have used the '-s' option.
>
> root@machine-4:/home# lxc-ls -f
> NAME STATEIPV4IPV6 GROUPS AUTOSTART
> -
> *worker RUNNING 10.0.3.109 - - NO *
>
>
i have used the '-s' option.
root@machine-4:/home# lxc-ls -f
NAME STATEIPV4IPV6 GROUPS AUTOSTART
-
*worker RUNNING 10.0.3.109 - - NO *
root@machine-4:/home# *lxc-checkpoint -s* -D /home/ImGLXC1Worker -n worker
r
on Ubuntu I created a upstart conf to handle it
Here is the upstart file I use:
description "start unpriv containers"
start on started lxc
script
USERS="mike"
for u in $USERS; do
cgm create all lxc$u
cgm chown all lxc$u $(id -u $u) $(id -g $u)
lxc-autostart -L -
Here is /usr/local/bin/startunprivlx:
#!/bin/sh
cgm movepid all $1 $$
sudo -iH -u $2 -- lxc-start -n $3 -d
On 01/03/2015 12:17 PM, Nicholas J Ingrassellino wrote:
I am trying to get unprivileged containers to autostart without success. The
built-in mechanisms do not work nor does cron. I have
I was able to resolve the lock issue, today. It seems like the environment
variable XDG_RUNTIME_DIR holds the value of that directory per-user. while
using sudo it didn't change the directory, and still set to the login user.
I found the correct directory using `ls -alh /run/user/*` (the one thats
I am having the same issue.
After an
/sudo su - lxc/
I try using
/lxc-create/
. I get
/lxc-create: Permission denied - failed to create directory
'/run/user/1000/lock/'//
/
which is the uid of the "logged in" user. I am writing up instructions
to host a how-to on my blog and
I am trying to get unprivileged containers to autostart without success.
The built-in mechanisms do not work nor does cron. I have Google'ed and
found many people with the same issue but no solution.
Since this is such a common issue I take it there is no solution
currently? That sounds odd to
On Sat, Jan 03, 2015 at 02:00:45PM +0100, Thouraya TH wrote:
> i didn't run with -v:
>
> i have in the restore.log file:
> Warn (cr-restore.c:996): Set CLONE_PARENT | CLONE_NEWPID but it might
> cause restore problem,because not all kernels support such clone flags
> combinations!
> RTNETLINK ans
i didn't run with -v:
i have in the restore.log file:
Warn (cr-restore.c:996): Set CLONE_PARENT | CLONE_NEWPID but it might
cause restore problem,because not all kernels support such clone flags
combinations!
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File ex
