PBS dont start on v4

[DjSni]

Hi,

when I update to v4, I get the following message in the log: get_network_interfaces failed - could not deserialize ip link output
I don't know why, but when I go into the container, I get the following via ip a:

154: eth0@if155: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:ac:14:00:11 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.20.0.17/16 brd 172.20.255.255 scope global eth0
       valid_lft forever preferred_lft forever

Docker log:

Unable to open syslog: Os { code: 2, kind: NotFound, message: "No such file or directory" }
Error: mkstemp "/run/proxmox-backup/proxy.tmp_XXXXXX" failed: ENOENT: No such file or directory
Unable to open syslog: Os { code: 2, kind: NotFound, message: "No such file or directory" }
catching shutdown signal    
catching reload signal    
Unable to open syslog: Os { code: 2, kind: NotFound, message: "No such file or directory" }
catching shutdown signal    
catching reload signal    
get_network_interfaces failed - could not deserialize ip link output
applied rrd journal (1689 entries in 0.014 seconds)    
rrd journal successfully committed (15 files in 0.030 seconds)    
PROXY: Starting...
CRON: Starting...
/etc/proxmox-backup is a mountpoint
/var/lib/proxmox-backup is a mountpoint
/var/log/proxmox-backup is a mountpoint
/run is a mountpoint
API: Starting...
PROXY: Starting...
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
...

Docker run:

docker run -d
  --name='proxmox-backup-server'
  --net='skynet'
  --pids-limit 4096
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="XXX"
  -e HOST_CONTAINERNAME="proxmox-backup-server"
  -e 'TZ'='Europe/Berlin'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:8007]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/devzwf/unraid-docker-templates/main/images/pbs-logo.jpg'
  -p '8007:8007/tcp'
  -v '/mnt/user/docker/appdata/pbs/etc':'/etc/proxmox-backup':'rw'
  -v '/mnt/user/docker/appdata/pbs/logs':'/var/log/proxmox-backup':'rw'
  -v '/mnt/user/docker/appdata/pbs/lib':'/var/lib/proxmox-backup':'rw'
  -v '/mnt/disk3/Sicherung/Server/Proxmox/':'/backups':'rw'
  --restart unless-stopped
  --memory=2g
  --cap-add SYS_RAWIO
  --mount type=tmpfs,destination=/run 'ayufan/proxmox-backup-server:beta'

[ayufan]

Interesting. I updated my docker-compose, and it seems to work fine, but I see that I have network_mode: host.

[ayufan]

@DjSni This seems to be the command: https://github.com/proxmox/proxmox-rs/blob/0232b0162c30efbf00dd6c0a488114ffb487408b/proxmox-network-api/src/config/helper.rs#L209.

Can you try to run it in docker container?

[ayufan]

I just run on my dev arm64 machine:

root@debian:/opt/pve-backup-server-dockerfiles# docker-compose logs -f
WARN[0000] /opt/pve-backup-server-dockerfiles/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
pbs-1  | PROXY: Starting...
pbs-1  | CRON: Starting...
pbs-1  | rm: cannot remove '/etc/proxmox-backup/.*.lck': No such file or directory
pbs-1  | /etc/proxmox-backup is a mountpoint
pbs-1  | /var/lib/proxmox-backup is a mountpoint
pbs-1  | /var/log/proxmox-backup is a mountpoint
pbs-1  | /run is a mountpoint
pbs-1  | API: Starting...
pbs-1  | Unable to open syslog: Os { code: 2, kind: NotFound, message: "No such file or directory" }
pbs-1  | Unable to open syslog: Os { code: 2, kind: NotFound, message: "No such file or directory" }
pbs-1  | applied rrd journal (50 entries in 0.003 seconds)    
pbs-1  | catching shutdown signal    
pbs-1  | catching reload signal    
pbs-1  | catching shutdown signal    
pbs-1  | catching reload signal    
pbs-1  | rrd journal successfully committed (12 files in 0.005 seconds)    

[DjSni]

I changed the network mode to host, and now it seems to be working.
But I'm still getting the same errors:

Unable to open syslog: Os { code: 2, kind: NotFound, message: ‘No such file or directory’ }
Error: mkstemp ‘/run/proxmox-backup/proxy.tmp_XXXXXX’ failed: ENOENT: No such file or directory
Unable to open syslog: Os { code: 2, kind: NotFound, message: ‘No such file or directory’ }
catching shutdown signal    
catching reload signal    
Unable to open syslog: Os { code: 2, kind: NotFound, message: ‘No such file or directory’ }
catching shutdown signal    
catching reload signal    
get_network_interfaces failed - could not deserialise ip link output
applied rrd journal (2340 entries in 0.013 seconds)    
rrd journal successfully committed (15 files in 0.029 seconds)    
PROXY: Starting...
CRON: Starting...
/etc/proxmox-backup is a mountpoint
/var/lib/proxmox-backup is a mountpoint
/var/log/proxmox-backup is a mountpoint
/run is a mountpoint
API: Starting...
PROXY: Starting...
get_network_interfaces failed - could not deserialise ip link output
authentication failure; rhost=[::ffff:10.x.x.x]:56030 user=admin@pbs msg=invalid credentials    
POST /api2/json/access/ticket: 401 Unauthorised: [client [::ffff:10.x.x.x]:56030] permission check failed.    
get_network_interfaces failed - could not deserialize ip link output
get_network_interfaces failed - could not deserialize ip link output
...

[ayufan]

So, still the same problem. What kernel version? Maybe this is problem?

[DjSni]

So, still the same problem. What kernel version? Maybe this is problem?

Unraid Version 7.2.0-beta.1
Kernel Linux 6.12.40-Unraid

[ayufan]

Can you post ip -details -json link show from non-host-mode and host-mode from within container? You might want to anonymise mac-address. IP is likely fine, unless it is not public facing IPv6.

[DjSni]

Can you post ip -details -json link show from non-host-mode and host-mode from within container? You might want to anonymise mac-address. IP is likely fine, unless it is not public facing IPv6.

Yes, Normal-Mode:

redacted

Host-Mode:

redacted

[ayufan]

@DjSni

I think the --net='skynet' might be the problem. Unsure. I don't see anything that would not deserialize.

[ayufan]

@DjSni The problem is tunl0 interface. The address cannot be expanded to MacAddress type.

{
  "ifname": "tunl0",
  "altnames": null,
  "ifindex": 2,
  "link_type": "ipip",
  "address": "0.0.0.0",
  "linkinfo": {
    "info_slave_data": {
      "perm_hw_addr": null
    },
    "info_kind": "ipip"
  },
  "operstate": "DOWN"
}

[DjSni]

I seem to get the error message in host mode and net mode, but now I also see a web interface in net mode. But apparently I'm not the only one with this problem:

https://forum.proxmox.com/threads/proxmox-backup-proxy-seemingly-crashes-after-being-accessed-through-reverse-proxy-after-update-to-4-0.169313/
https://forum.proxmox.com/threads/proxmox-backup-server-4-0-released.169306/#post-789040

[ayufan]

@DjSni The problem is this ipip interface, the tunl0.

[DjSni]

Oh, well, the interface is in both mods with the tun10, so it's definitely an UnRaid problem, since every container can be connected to Tailscale.

[ayufan]

I don't understand why this is needed in a container. You can not add the `--net`, rather use `--ports`. It should work as well, and you should be able to access PBS via UnRaid IP over 8007 port.

…

On Sat, 9 Aug 2025 at 22:20, DjSni ***@***.***> wrote: *DjSni* left a comment (ayufan/pve-backup-server-dockerfiles#84) <#84 (comment)> Oh, well, the interface is in both mods with the tun10, so it's definitely an UnRaid problem, since every container can be connected to Tailscale. — Reply to this email directly, view it on GitHub <#84 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASOSQITLSZENOVAXZN4MN33MZJYLAVCNFSM6AAAAACDQIBLTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZSGA3TINZXGI> . You are receiving this because you commented.Message ID: ***@***.***>