Gabe,
Temporarily putting the useradd program building work aside, on my target platform I did the following steps as you mentioned. The “lxc-attach -n femtolxc” execution ends up with failures. Listed below is what I have so far.
I am resolving the failure. Your comment is absolutely welcome.
root@phyFLEX-i:~ lxc-checkconfig
— Namespaces —
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
Network namespace: enabled
Multiple /dev/pts instances: enabled
— Control groups —
Cgroup: enabled
Cgroup clone_children flag: enabled
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: missing
Cgroup cpuset: enabled
— Misc —
Veth pair device: enabled
Macvlan: enabled
Vlan: enabled
File capabilities: missing
enabled
Note : Before booting a new kernel, you can check its configuration
usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
root@phyFLEX-i:~ lxc-create -n femtolxc
’femtolxc’ created
root@phyFLEX-i:~ lxc-start -n femtolxc
root@phyFLEX-i:~ lxc-info -n femtolxc
state: RUNNING
pid: 3510
root@phyFLEX-i:~ lxc-attach -n femtolxc
lxc-attach: No such file or directory - failed to open '/proc/3510/ns/pid’
lxc-attach: failed to enter the namespace
root@phyFLEX-i:~