Try adding lxc.mount option into container config using following
mount point file:
sysfs sys sysfs ro,defaults 0 0
proc proc proc nodev,noexec,nosuid 0 0
/proc/sys ${rootfs_path}/proc/sys none ro,bind 0 0
2013/3/13 John Lane :
> Good morning, I am trying to get LXC guests working with systemd.
2013/3/13 John :
> On 13/03/13 11:58, Kay Sievers wrote:
>>
>> On the host, "newinstance" is not strictly needed, it is useful inside the
>> container though.
>
> How do I make it use newinstance inside the container? is that a lxc config
> or systemd?
lxc does this explicitly during container star
Seems like remote command execution was broken somewhere around systemd 213
Remote access to systemd 212 host:
[root@host1 ~]# systemctl --version
systemd 212
+PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
+SECCOMP -APPARMOR
$ systemctl -H idkfa@host1 status
Enter passphrase
You could just use /etc/systemd/system/unison@instance.service.d/
directory to provide service environment variables, this seems to be
much more convenient way to configure service.
Best regards,
Alexander
2014-06-29 0:15 GMT+08:00 Moviuro :
> Hi all,
>
> I am at the moment trying to clean up my
%I specifier unescapes instance name, so
unison@path-to-profile.service instance becomes "path/to/profile"
Best regards,
Alexander
2014-06-29 0:31 GMT+08:00 Moviuro :
> On Sunday 29 June 2014 00:21:33 you wrote:
>> You could just use /etc/systemd/system/unison@instance.service.d/
>> directory to
