On Wednesday, July 12, 2017 20:33 JST, "Tomasz Chmielewski" wrote: > In the last days, lxc commands are failing randomly. > > Example (used in a script): > > # lxc config set TDv2-z-testing-a19ea62218-2017-07-12-11-23-03 raw.lxc > lxc.aa_allow_incomplete=1 > error: not found > > It shouldn't fail, because: > > # lxc list|grep TDv2-z-testing-a19ea62218-2017-07-12-11-23-03 > | TDv2-z-testing-a19ea62218-2017-07-12-11-23-03 | STOPPED | > | | > PERSISTENT | 0 |
To be more specific: it only seems to fail on "lxc config" command (lxc config set, lxc config edit, lxc config device add). My container startup script work like below: lxc copy container-template newcontainer lxc config set newcontainer raw.lxc "lxc.aa_allow_incomplete=1" ...lots of lxc file pull / push... lxc config show newcontainer | sed -e "s/$BRIDGE_OLD/$BRIDGE_NEW/" | lxc config edit newcontainer ...again, lots of lxc file pull / push... lxc config device add newcontainer uploads disk source=/some/path path=/var/www/path It only fails with "error: not found" on the first, second or third "lxc config" line. It started to fail in the last 2 weeks I think (lxd updates?) - before, it was rock solid. Tomasz Chmielewski https://lxadm.com _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
