Open skidoomanubuntu opened 1 year ago
Hi @skidoomanubuntu,
We recently fixed that endless loop in snapcraft 7.5.4. With that version, snapcraft should timeout and warn about network issues.
This error occurs when the LXD container doesn't have network access. This can be caused by a VPN or Docker being installed on the same system. Do you happen to have Docker installed?
Bug Description
I have a snap for Core 22 that builds like a charm on x86. However, when I am trying to build on ARM, it fails.
I believe it gets blocked at lxd stage.
To Reproduce
You can check out the code from here:
git@github.com:skidoomanubuntu/oval-core-tools.git
Then, just snapcraft on an ARM machine
BTW, I tried a few variations. Going to multipass was not successful, neither was invoking sudo snapcraft.
Environment
I have an ARM server with 64 cores from ADLink, so I assume my system's scalability is not an issue.
uname -r: 5.4.0-155-generic
lscpu: Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 1 Core(s) per socket: 64 Socket(s): 1 NUMA node(s): 1 Vendor ID: ARM Model: 1 Model name: Neoverse-N1 Stepping: r3p1 CPU max MHz: 2200.0000 CPU min MHz: 1000.0000 BogoMIPS: 50.00 L1d cache: 4 MiB L1i cache: 4 MiB L2 cache: 64 MiB NUMA node0 CPU(s): 0-63 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Mmio stale data: Not affected Vulnerability Retbleed: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1: Mitigation; __user pointer sanitization Vulnerability Spectre v2: Mitigation; CSV2, BHB Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
snapcraft.yaml
Relevant log output
Additional context
No response