Closed MikePooh closed 1 year ago
Are you trying to run this in a Docker container? That is currently not supported. Never been tested there. Maybe you can get it to work by opening more/all ports?
Nope. I am trying just to launch it on the OS itself, not in the container.
I am confused with this line after which it exists
2023/04/14 13:28:42 zeroconf: Failed to initialize resolver: listen udp6 [ff02::]:5353: socket: address family not supported by protocol
may it be the root of the problem?
Possibly. Do you have some unusual network configuration?
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 3c:97:0e:85:b4:b9 brd ff:ff:ff:ff:ff:ff
altname enp4s0
inet 192.168.11.3/24 brd 192.168.11.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:90:a2:f6:64:73 brd ff:ff:ff:ff:ff:ff
altname wlp3s0
inet 192.168.0.7/24 brd 192.168.0.255 scope global dynamic noprefixroute wlan0
valid_lft 210557sec preferred_lft 210557sec
4: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet 192.168.47.1/32 scope global wg0
valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:1c:21:6b:32 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
9: vethcc46e05@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 4e:1e:66:6f:f6:39 brd ff:ff:ff:ff:ff:ff link-netnsid 0
Maybe it's tripping over wg0, docker0, vethcc... - just for testing, can you remove/disable those devices and see if it changes anything?
It seems like the issue is that appimaged
can't set up the zeroconf and calls log.Fatal
. This should probably be changed to a simple log message, or at most a desktop notification.
journalctl --user -u appimaged.service
Linux Mint 21.1 Vera x64 Linux kernel 5.15.0-69