Failed to change ACLs ERROR after re-install using snap on archlinux and lxd recover

LXD
1

Error: Failed to handle idmapped storage: invalid argument - Failed to change ACLs on /var/snap/lxd/common/lxd/storage-pools/lxdstoragepool/containers/arlanger/rootfs/var/log/journal

My host is archlinux as was my previous host.

storage pool is lxdstoragepool and I have 3 containers: 1 ubuntu container and 2 archlinux containers.

I did an lxd recoverafter changing my host to another partition. However, I ended up removing lxd on the new host and re-installing using snap.

After performing lxd recover, I was able to successfully remap an ubuntu container:
lxc launch rails

A month later I tried to launch an arch based container:
lxc launch rusty
Which gave me the error shown above.

$ lxc info --show-log rusty
Name: rusty
Status: STOPPED
Type: container
Architecture: x86_64
Created: 2021/03/29 03:00 EDT
Last Used: 2021/12/24 06:23 EST

Log

$ lxc info --show-log rails
Name: rails
Status: RUNNING
Type: container
Architecture: x86_64
PID: 558488
Created: 2021/03/31 23:48 EDT
Last Used: 2022/01/12 10:24 EST

Resources:
  Processes: 98
  CPU usage:
    CPU usage (in seconds): 21
  Memory usage:
    Memory (current): 748.52MiB
  Network usage:
    docker0:
      Type: broadcast
      State: UP
      MAC address: 02:42:aa:ed:dd:ca
      MTU: 1500
      Bytes received: 0B
      Bytes sent: 0B
      Packets received: 0
      Packets sent: 0
      IP addresses:
        inet:  172.17.0.1/16 (global)
    eth0:
      Type: broadcast
      State: UP
      Host interface: vethea2b1676
      MAC address: 00:16:3e:db:b1:13
      MTU: 1500
      Bytes received: 42.68kB
      Bytes sent: 22.43kB
      Packets received: 79
      Packets sent: 71
      IP addresses:
        inet:  10.127.202.21/24 (global)
        inet6: fd42:5b3b:2863:6328:216:3eff:fedb:b113/64 (global)
        inet6: fe80::216:3eff:fedb:b113/64 (link)
    lo:
      Type: loopback
      State: UP
      MTU: 65536
      Bytes received: 501.62kB
      Bytes sent: 501.62kB
      Packets received: 1485
      Packets sent: 1485
      IP addresses:
        inet:  127.0.0.1/8 (local)
        inet6: ::1/128 (local)

Snapshots:
+-----------------------------------+----------------------+------------+----------+
|               NAME                |       TAKEN AT       | EXPIRES AT | STATEFUL |
+-----------------------------------+----------------------+------------+----------+
| railsBAK01                        | 2021/07/15 03:35 EDT |            | NO       |
+-----------------------------------+----------------------+------------+----------+
| xenial-ruby243p205-rail514-psql95 | 2017/12/15 00:15 EST |            | NO       |
+-----------------------------------+----------------------+------------+----------+

Log:

lxc rails 20220112152409.902 WARN     conf - conf.c:lxc_map_ids:3579 - newuidmap binary is missing
lxc rails 20220112152409.902 WARN     conf - conf.c:lxc_map_ids:3585 - newgidmap binary is missing
lxc rails 20220112152409.903 WARN     conf - conf.c:lxc_map_ids:3579 - newuidmap binary is missing
lxc rails 20220112152409.903 WARN     conf - conf.c:lxc_map_ids:3585 - newgidmap binary is missing

$ sudo su
ls -l /var/snap/lxd/common/lxd/storage-pools/lxdstoragepool/
total 0
2

i’ve got the exact same error with 1 of my containers. Did you resolved it?

Jef

3

Hi, sorry for the late reply, I logged on yesterday and then was torn to find out that stgraber has moved on then forgot to reply to you.

Unfortunately, my equipment was stolen shortly after making this post and so I am not sure if i ever resolved it.

Sorry and good luck. Hope you find the solution.

4

I deleted this /var/log/journal directory (recursive) on the working backup container. Then I copied the container back to the operational server and the problem was solved.
This gives me the feeling that the whole LXD stuff is far from finished…

Jef