Error spinning up LXD containers for Snapcraft

While building a new version of Snapcraft, I get an error from spinning up the build containers. Here’s the logs:

» lxc info --project snapcraft --show-log local:snapcraft-snapcraft-on-amd64-for-amd64-26090235
Name: snapcraft-snapcraft-on-amd64-for-amd64-26090235
Status: STOPPED
Type: container
Architecture: x86_64
Created: 2024/11/06 16:53 EST
Last Used: 2024/11/07 09:09 EST

Log:

lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.589 WARN     idmap_utils - ../src/src/lxc/idmap_utils.c:lxc_map_ids:165 - newuidmap binary is missing
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.589 WARN     idmap_utils - ../src/src/lxc/idmap_utils.c:lxc_map_ids:171 - newgidmap binary is missing
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.590 WARN     idmap_utils - ../src/src/lxc/idmap_utils.c:lxc_map_ids:165 - newuidmap binary is missing
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.590 WARN     idmap_utils - ../src/src/lxc/idmap_utils.c:lxc_map_ids:171 - newgidmap binary is missing
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.646 ERROR    cgfsng - ../src/src/lxc/cgroups/cgfsng.c:cgfsng_mount:2417 - No such file or directory - Failed to create cgroup at_mnt 24()
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.646 ERROR    conf - ../src/src/lxc/conf.c:lxc_mount_auto_mounts:655 - No such file or directory - Failed to mount "/sys/fs/cgroup"
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.646 ERROR    conf - ../src/src/lxc/conf.c:lxc_setup:3936 - Failed to setup remaining automatic mounts
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.646 ERROR    start - ../src/src/lxc/start.c:do_start:1273 - Failed to setup container "snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235"
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.646 ERROR    sync - ../src/src/lxc/sync.c:sync_wait:34 - An error occurred in another process (expected sequence number 4)
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.654 WARN     network - ../src/src/lxc/network.c:lxc_delete_network_priv:3671 - Failed to rename interface with index 0 from "eth0" to its initial name "veth5ec8d5db"
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.654 ERROR    lxccontainer - ../src/src/lxc/lxccontainer.c:wait_on_daemonized_start:837 - Received container state "ABORTING" instead of "RUNNING"
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.654 ERROR    start - ../src/src/lxc/start.c:__lxc_start:2114 - Failed to spawn container "snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235"
lxc snapcraft_snapcraft-snapcraft-on-amd64-for-amd64-26090235 20241107140911.654 WARN     start - ../src/src/lxc/start.c:lxc_abort:1037 - No such process - Failed to send SIGKILL via pidfd 19 for process 144240
lxc 20241107140911.809 ERROR    af_unix - ../src/src/lxc/af_unix.c:lxc_abstract_unix_recv_fds_iov:218 - Connection reset by peer - Failed to receive response
lxc 20241107140911.809 ERROR    commands - ../src/src/lxc/commands.c:lxc_cmd_rsp_recv_fds:128 - Failed to receive file descriptors for command "get_init_pid"

Here’s my default profile:

» lxc profile show default                                                 
name: default
description: Default LXD profile
config:
  raw.idmap: both 1000 0
devices:
  eth0:
    name: eth0
    network: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
used_by:
- /1.0/instances/snapcraft-dev
- /1.0/instances/jammy

And just in case it’s helpful, here’s some platform info:

» uname -a 
Linux magnolia 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Thanks for any help!

Hi

Please see https://documentation.ubuntu.com/lxd/en/latest/faq/#why-does-starting-containers-suddenly-fail

This should explain whats going on. I believe its your VPN client.

2 Likes