Snapcraft

  1. Bug #1999321
  2. Comment #6

Comment 6 for bug 1999321

Revision history for this message
Claudio André (claudioandre.br) wrote :

The tip that the problem is related to network access saved my day. In my case, the firewall was preventing LXD from working properly. Disabling the firewall (or fixing the rules) does the trick.

Yesterday:
`
[UFW BLOCK] IN=lxdbr0 OUT= PHYSIN=vethd728cd65 MAC=00:16:3e:83:1c:fd:00:16:3e:b4:de:c7:86:dd SRC=fe80:0000:0000:0000:0216:3eff:feb4:dec7 DST=fe80:0000:0000:0000:0216:3eff:fe83:1cfd LEN=78 TC=0 HOPLIMIT=64 FLOWLBL=1016275 PROTO=UDP SPT=42222 DPT=53 LEN=38
`
Now:
`
UFW BLOCK] IN=lxdbr0 OUT= PHYSIN=vethe4c2b3ac MAC=00:16:3e:83:1c:fd:00:16:3e:b4:de:c7:86:dd SRC=fe80:0000:0000:0000:0216:3eff:feb4:dec7 DST=fe80:0000:0000:0000:0216:3eff:fe83:1cfd LEN=78 TC=0 HOPLIMIT=64 FLOWLBL=759663 PROTO=UDP SPT=59514 DPT=53 LEN=38
`

Could you guys add an alert the end user to make our life easier?

- I am on Ubuntu 22, snapping for core22, snapcraft via snap.