Snapcraft fails using LXD on NVIDIA Jetson TX2

snapcraft
31

And with enough persistence, it appears I have prevailed (EDIT: I haven’t…intermittent success at least)

I used the recommendations to set the raw.lxc parameters from this issue I referenced above. However lxc config edit test complained about formatting issues when adding in the raw.lxc section. Then I found this issue which describes how many of the raw.lxc parameters were either renamed or removed.

I came up with the following modifications to my config:

uskellse@uskellse-tx2:~$ lxc config show test
architecture: aarch64
config:
  image.architecture: arm64
  image.description: ubuntu 18.04 LTS arm64 (release) (20200519.1)
  image.label: release
  image.os: ubuntu
  image.release: bionic
  image.serial: "20200519.1"
  image.type: squashfs
  image.version: "18.04"
  raw.lxc: |-
    lxc.apparmor.profile=unconfined
    lxc.cgroup.devices.allow=a
    lxc.mount.auto=proc:rw sys:ro cgroup:ro
    lxc.autodev=1
  security.privileged: "true"
  volatile.base_image: 134c9aa1abc870990921923735509b01ccbad69481d957b74d65e090511c9c9f
  volatile.eth0.host_name: veth7cc63258
  volatile.eth0.hwaddr: 00:16:3e:dd:5f:fb
  volatile.idmap.base: "0"
  volatile.idmap.current: '[]'
  volatile.idmap.next: '[]'
  volatile.last_state.idmap: '[]'
  volatile.last_state.power: RUNNING
devices: {}
ephemeral: false
profiles:
- default
stateful: false
description: ""

And (after restarting the container) I’m able to do snapcraft --destructive-mode from inside the LXD container and see it through to completion!

I’m not sure this really solves my LXD problems, but my objectives have been achieved. Thanks for your help/patience everyone.

1 Like