Kernel and Nvidia driver update leads to broken Docker container

Exact same issue here. First of all my docker container that rely on my gpu stop working, then after downgrading the 380 nvidia driver to 375 or 370 lightdm no longer starts.

Timeshift to the rescue. I still have no idea what is going wrong but this updates seems to cause quite some pain :frowning:

Yes

This was expected because major changes to KDE and GNOME were released simultaneously.

However, this didn’t stop some people from pestering the team almost daily to finally release an update. (The threads are easy to find.) Let’s assume, for the sake of argument, that these weren’t the same people who are now complaining that one thing or another isn’t working. (And indeed, it’s usually other users who are affected.)

Due to the long wait for the update, significantly more problems have accumulated. But everything will surely be sorted out again in the coming days and weeks.
:footprints:

And thanks to btrfs, timeshift, and the option for a second kernel, the damage is usually kept to a minimum.

1 Like

Do you also have an idea how to get the update installed without breaking the system?

Yes, at the risk of repeating, or at least paraphrasing every person who has published how tos on the subject.

Maintain your system, keep it clean, don’t use lots of AUR packages, if you do remove them before the update, reinstall after.

Read the documentation, before starting.

if you do all of that, it should not matter if you use pamac-manager, pamac in the cli, or pacman.

Personally I find that pamac-manager works just fine, if I do all of the above.

Did that but it still broke docker using my GPU. After that downgrading the driver broke lightdm. I can repeat that again but I doubt I’ll get a different outcome. Has anyone had issues with docker as well? How did you solve them?

You should start a new thread for this. Supply information using

inxi -zv8

Copy tha output from that, and paste it into the page using the </> button or by placing three back ticks on the line before your paste, and three back ticks on the line after your paste.

I moved the topic to a separate thread.

GPU pass-through into docker is a complicated process.

I suggest you research the configuration for your explicit use case.

With certain specialised projects even small changes in applications or drivers may cause the project to malfunction.

I am guessing you are running an AI project in docker which depends on Nvidia GPU - perhaps the upstream project know which knobs to adjust.

An incident like you describe may be why certain projects tend to support Red Hat and Ubuntu - but not Arch Linux and derivatives like Manjaro - we are simply too unstable - even when using stable branch - in context of the project.

Is it? From my experience, a `–gpus` parameter is sufficient.

1 Like

First of all what is this title? Why do you assume poor maintenance here? Why do you make this look like it’s my fault?

I followed all the recommended steps and the kernel / driver update combo broke stuff that was running for months.

I always apply updates to images and the os after checking changes. Reverting the os update resolved the issue. This is not a docker or GPU passthrough issue. This is a broken os update.

I’ll provide info when I’m back home - potentially tomorrow as I’m still traveling.

Here you go. This version of kernel / Nvidia driver runs just fine.

System:
  Kernel: 6.18.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18-x86_64
    root=UUID=86ad2543-5b6f-4f9f-b63f-7518886db958 rw apparmor=1 delayacct
    security=apparmor udev.log_priority=3
  Desktop: Cinnamon v: 6.4.13 tk: GTK v: 3.24.51 wm: Muffin v: 6.4.1 tools:
    avail: cinnamon-screensaver dm: LightDM v: 1.32.0 Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG B550 TOMAHAWK (MS-7C91) v: 2.0
    serial: <filter> uuid: a89f7277-b343-1512-ab8b-d8bbc136bbd5 Firmware: UEFI
    vendor: American Megatrends LLC. v: A.C0 date: 03/06/2023
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 64 GiB available: 62.72 GiB used: 8.24 GiB (13.1%)
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 2667 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Crucial
    part-no: BL16G32C16U4B.M16FE1 serial: <filter>
  Device-2: Channel-A DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 2667 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Crucial
    part-no: BL16G32C16U4B.16FE serial: <filter>
  Device-3: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 2667 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Crucial
    part-no: BL16G32C16U4B.M16FE1 serial: <filter>
  Device-4: Channel-B DIMM 1 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 2667 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Crucial
    part-no: BL16G32C16U4B.16FE serial: <filter>
PCI Slots:
  Slot: 0 type: PCIe status: in use info: J6B2 length: long volts: 3.3
    bus-ID: 00:01.0
  Slot: 1 type: PCIe status: in use info: J6B1 length: short volts: 3.3
    bus-ID: 00:1c.3
  Slot: 2 type: PCIe status: in use info: J6D1 length: short volts: 3.3
    bus-ID: 00:1c.4
  Slot: 3 type: PCIe status: in use info: J7B1 length: short volts: 3.3
    bus-ID: 00:1c.5
  Slot: 4 type: PCIe status: in use info: J8B4 length: short volts: 3.3
    bus-ID: 00:1c.6
  Slot: 5 type: PCIe status: in use info: J8D1 length: short volts: 3.3
    bus-ID: 00:1c.7
  Slot: 6 type: PCI status: in use info: J8B3 length: short volts: 3.3
    bus-ID: 00:1e.0
  Slot: 12 type: PCIe status: in use info: J10 length: short volts: 3.3
    bus-ID: 00:03.1 children: 1: 2b:00.0 class-ID: 0300 type: display 2: 2b:00.1
    class-ID: 0403 type: audio
  Slot: 14 type: PCIe status: in use info: J3700, M.2 length: short
    volts: 3.3 bus-ID: 00:01.1 children: 1: 01:00.0 class-ID: 0108
    type: mass-storage
  Slot: 128 type: PCIe status: in use info: J3708 length: short volts: 3.3
    bus-ID: 03:00.0
  Slot: 134 type: PCIe status: available info: J3703 length: short
    volts: 3.3 bus-ID: 00:1f.7
  Slot: 135 type: PCIe status: in use info: J3702 length: short volts: 3.3
    bus-ID: 03:07.0
  Slot: 132 type: PCIe status: available info: J3707 length: short
    volts: 3.3 bus-ID: 00:1f.7
  Slot: 137 type: PCIe status: in use info: J3701, M.2 length: short
    volts: 3.3 bus-ID: 03:09.0
CPU:
  Info: model: AMD Ryzen 7 5800X socket: AM4 bits: 64 type: MT MCP
    arch: Zen 3+ gen: 3 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA20102E
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 1754 min/max: 556/4854 boost: enabled
    base/boost: 3800/4850 scaling: driver: amd-pstate-epp governor: powersave
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 1754 2: 1754 3: 1754 4: 1754
    5: 1754 6: 1754 7: 1754 8: 1754 9: 1754 10: 1754 11: 1754 12: 1754
    13: 1754 14: 1754 15: 1754 16: 1754 bogomips: 121607
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip
    user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
    vpclmulqdq wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt
    xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Gigabyte
    driver: nvidia v: 580.105.08 alternate: nouveau,nova_core,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
    arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: none off: DP-1,HDMI-A-1
    empty: DVI-D-1,DVI-D-2 bus-ID: 2b:00.0 chip-ID: 10de:1c03 class-ID: 0300
  Device-2: Microsoft LifeCam VX-2000 driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:3
    chip-ID: 045e:0761 class-ID: 0102
  Display: x11 server: X.Org v: 21.1.21 with: Xwayland v: 24.1.9 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3640x1920 s-dpi: 96 s-size: 963x508mm (37.91x20.00")
    s-diag: 1089mm (42.87")
  Monitor-1: DP-1 mapped: DP-0 note: disabled pos: primary,bottom-r
    model: BenQ GL2706PQ serial: <filter> built: 2016 res: mode: 2560x1440
    hz: 60 scale: 100% (1) dpi: 109 gamma: 1.2 chroma: red: x: 0.651 y: 0.337
    green: x: 0.314 y: 0.627 blue: x: 0.149 y: 0.051 white: x: 0.314 y: 0.329
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 2560x1440, 2048x1280, 1920x1200, 1920x1080, 1600x1200, 1680x1050,
    1600x1000, 1600x900, 1280x1024, 1440x900, 1280x720, 1024x768, 800x600,
    720x576, 720x480, 640x480
  Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: top-left
    model: BenQ GL2460 serial: <filter> built: 2017 res: mode: 1920x1080 hz: 60
    scale: 177% (0.5625) to: 1080x1920 dpi: 92 gamma: 1.2 chroma: red:
    x: 0.643 y: 0.333 green: x: 0.333 y: 0.624 blue: x: 0.153 y: 0.047 white:
    x: 0.314 y: 0.329 size: 531x299mm (20.91x11.77") diag: 609mm (24")
    ratio: 16:9 modes: 1920x1080, 1680x1050, 1600x900, 1280x1024, 1280x800,
    1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.105.08
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1060
    6GB/PCIe/SSE2 memory: 5.86 GiB
  API: Vulkan v: 1.4.328 layers: 2 device: 0 type: discrete-gpu name: NVIDIA
    GeForce GTX 1060 6GB driver: nvidia v: 580.105.08 device-ID: 10de:1c03
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    gpu: nvidia-settings,nvidia-smi x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GP106 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 2b:00.1 chip-ID: 10de:10f1 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 2d:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Kingston HyperX Cloud Stinger Wireless
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-1:2 chip-ID: 0951:16da class-ID: 0300
  Device-4: Microsoft LifeCam VX-2000 driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:3
    chip-ID: 045e:0761 class-ID: 0102
  API: ALSA v: k6.18.0-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.9 status: n/a (root, process) tools: pw-cli
  Server-3: PulseAudio v: 17.0-93-gbe2efb status: active (root, process)
    with: 1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
    tools: pacat,pactl,pavucontrol
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp5s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 2a:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp42s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: br-0945b599233a state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-2: br-47425c0bd684 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-3: br-50020bc7608e state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-4: br-6cc693103434 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-5: br-8d39dd95d400 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-6: br-9538c0462cee state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-7: br-ab4446e5f79c state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-8: br-d14efb21fbcb state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-9: docker0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-10: veth057c62e state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-11: veth0bd6b28 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-12: veth0d63602 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-13: veth1ab9841 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-14: veth256ba88 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-15: veth37f8b85 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-16: veth4886b42 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-17: veth544bdb8 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-18: veth8a14135 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-19: veth8b387c7 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-20: vethaeb15b7 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-21: vethb5e58b1 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-22: vethb82c151 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-23: vethb873cdd state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-24: vethba8270c state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-25: vethe01214c state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-26: vethed571fb state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  Info: services: NetworkManager, sshd, systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:3
    chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 6.46 TiB used: 4.35 TiB (67.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:6 vendor: Lexar model: SSD NM790 4TB
    size: 3.73 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 16949 temp: 34.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 25.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 150 GiB size: 147.09 GiB (98.06%) used: 98.23 GiB (66.8%)
    fs: ext4 block-size: 4096 B dev: /dev/nvme1n1p5 maj-min: 259:5 label: N/A
    uuid: 86ad2543-5b6f-4f9f-b63f-7518886db958
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 31.3 MiB (32.6%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p1
    maj-min: 259:1 label: N/A uuid: 30CF-D74C
  ID-3: /home raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
    used: 1.47 TiB (82.0%) fs: ext4 block-size: 4096 B dev: /dev/sda1
    maj-min: 8:1 label: N/A uuid: e298188c-af0e-4a61-b3ac-6d84d9f0345a
  ID-4: /home/<filter>/android raw-size: 3.73 TiB size: 3.67 TiB (98.40%)
    used: 2.78 TiB (75.9%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p1
    maj-min: 259:7 label: N/A uuid: 59876845-08b6-4d82-960f-56256bbb8141
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swap
Unmounted:
  ID-1: /dev/nvme1n1p2 maj-min: 259:2 size: 16 MiB fs: N/A label: N/A
    uuid: N/A
  ID-2: /dev/nvme1n1p3 maj-min: 259:3 size: 780.6 GiB fs: ntfs label: BOOT
    uuid: 5270D23670D22111
  ID-3: /dev/nvme1n1p4 maj-min: 259:4 size: 822 MiB fs: ntfs
    label: Windows RE tools uuid: 28E0578CE0575F5E
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-2:2 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-4:3 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
    type: bluetooth driver: btusb interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 0a12:0001
    class-ID: e001
  Hub-3: 1-5:4 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-5.2:6 info: Metadot Das Keyboard 4 type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 24f0:204a class-ID: 0300
  Device-2: 1-6:5 info: Logitech Lightspeed Receiver
    type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c539 class-ID: 0300
  Device-3: 1-8:7 info: Micro Star MYSTIC LIGHT type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1462:7c91 class-ID: 0300
    serial: <filter>
  Hub-4: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-1:2 info: Kingston HyperX Cloud Stinger Wireless
    type: audio,HID driver: hid-generic,snd-usb-audio,usbhid interfaces: 4
    rev: 1.1 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 0951:16da class-ID: 0300
  Device-2: 3-3:3 info: Microsoft LifeCam VX-2000 type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 045e:0761 class-ID: 0102
  Hub-6: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 34.0 C mobo: 29.5 C gpu: nvidia temp: 24 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Repos:
  Packages: pm: pacman pkgs: 1920 libs: 457 tools: yay
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://manjaro.kurdy.org/stable/$repo/$arch
    2: https://mirror.23m.com/manjaro/stable/$repo/$arch
    3: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    4: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    5: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    6: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    7: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 519
  1: cpu: 105% command: python3 pid: 14805 mem: 33.3 MiB (0.0%)
  2: cpu: 100% command: ps pid: 14818 mem: 4.55 MiB (0.0%)
  3: cpu: 15.7% command: chrome pid: 13015 mem: 474.3 MiB (0.7%)
  4: cpu: 8.6% command: chrome pid: 13305 mem: 342.5 MiB (0.5%)
  5: cpu: 6.2% command: python3 pid: 2911 mem: 736.1 MiB (1.1%)
  Memory top: 5 of 519
  1: mem: 1379.5 MiB (2.1%) command: python pid: 3755 cpu: 5.0%
  2: mem: 736.1 MiB (1.1%) command: python3 pid: 2911 cpu: 6.2%
  3: mem: 474.3 MiB (0.7%) command: chrome pid: 13015 cpu: 15.7%
  4: mem: 342.5 MiB (0.5%) command: chrome pid: 13305 cpu: 8.6%
  5: mem: 339.4 MiB (0.5%) command: cinnamon pid: 8521 cpu: 5.1%
Info:
  Processes: 519 Power: uptime: 2m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 25.03 GiB services: csd-power,upowerd
    Init: systemd v: 258 default: graphical tool: systemctl
  Compilers: gcc: 15.2.1 Shell: Sudo (sudo) v: 1.9.17p2 default: Bash
    v: 5.3.8 running-in: gnome-terminal inxi: 3.3.40

It’s been running for months over multiple updates. It is the update that broke it.
It’s working again after restoring the timeshift backup.

I experimented with gpu passthrough for a virtual machine and it was quite complicated - my assumptions was it was equally complicated for a container - it is great if you can give a docker container access to the gpu just like that.

I stand corrected - :person_bowing:

When I split the topic of it was like this - no blame but a statement

image

I got that wrong. Sorry if I appeared rude.
I performed the upgrade in steps trying to isolate what packages are causing the docker container to fail to start.
The last batch I narrowed it down to is

[2025-12-19T21:47:11+0100] [PACMAN] Running 'pacman -Syu'
[2025-12-19T21:47:11+0100] [PACMAN] synchronizing package lists
[2025-12-19T21:47:11+0100] [PACMAN] starting full system upgrade
[2025-12-19T21:47:32+0100] [ALPM] running '60-mkinitcpio-remove.hook'...
[2025-12-19T21:47:33+0100] [ALPM] transaction started
[2025-12-19T21:47:33+0100] [ALPM] upgraded egl-x11 (1.0.3-1 -> 1.0.4-0)
[2025-12-19T21:47:34+0100] [ALPM] upgraded nvidia-utils (580.105.08-4 -> 580.119.02-1)
[2025-12-19T21:47:34+0100] [ALPM-SCRIPTLET] xorg configuration symlink valid...
[2025-12-19T21:47:34+0100] [ALPM] upgraded egl-wayland (4:1.1.20-1 -> 4:1.1.21-0)
[2025-12-19T21:47:34+0100] [ALPM] upgraded lib32-nvidia-utils (580.105.08-1 -> 580.119.02-1)
[2025-12-19T21:47:34+0100] [ALPM-SCRIPTLET] xorg configuration symlink valid...
[2025-12-19T21:47:34+0100] [ALPM] upgraded lightdm-slick-greeter (2.2.3-1 -> 2.2.5-1)
[2025-12-19T21:47:34+0100] [ALPM] upgraded lightdm-settings (2.0.9-1 -> 2.1.0-1)
[2025-12-19T21:47:34+0100] [ALPM-SCRIPTLET] 
[2025-12-19T21:47:34+0100] [ALPM-SCRIPTLET] ==> NOTE: We have enabled autologin for all users.
[2025-12-19T21:47:34+0100] [ALPM-SCRIPTLET] ==> NOTE: Reboot your system the first time, so changes will take affect.
[2025-12-19T21:47:34+0100] [ALPM-SCRIPTLET] 
[2025-12-19T21:47:35+0100] [ALPM] upgraded linux612 (6.12.61-1 -> 6.12.62-1)
[2025-12-19T21:47:35+0100] [ALPM] upgraded linux612-nvidia (580.105.08-5 -> 580.119.02-2)
[2025-12-19T21:47:35+0100] [ALPM] upgraded linux612-virtualbox-host-modules (7.2.4-8 -> 7.2.4-9)
[2025-12-19T21:47:36+0100] [ALPM] upgraded linux617 (6.17.11-1 -> 6.17.12-1)
[2025-12-19T21:47:36+0100] [ALPM] upgraded linux617-nvidia (580.105.08-7 -> 580.119.02-2)
[2025-12-19T21:47:36+0100] [ALPM] upgraded linux617-virtualbox-host-modules (7.2.4-10 -> 7.2.4-11)
[2025-12-19T21:47:37+0100] [ALPM] upgraded linux618 (6.18.0-1 -> 6.18.1-1)
[2025-12-19T21:47:37+0100] [ALPM] upgraded linux618-nvidia (580.105.08-2 -> 580.119.02-2)
[2025-12-19T21:47:37+0100] [ALPM] upgraded linux618-virtualbox-host-modules (7.2.4-2 -> 7.2.4-3)
[2025-12-19T21:47:37+0100] [ALPM] upgraded manjaro-cinnamon-settings (20250619-1 -> 20251210-1)
[2025-12-19T21:47:37+0100] [ALPM] upgraded nvidia-driver-assistant (0.22.105.08-1 -> 0.23.44.01-1)
[2025-12-19T21:47:37+0100] [ALPM] upgraded mhwd-nvidia (580.105.08-4 -> 580.119.02-1)
[2025-12-19T21:47:37+0100] [ALPM] upgraded nvidia-settings (580.105.08-4 -> 580.119.02-1)
[2025-12-19T21:47:37+0100] [ALPM] upgraded opencl-nvidia (580.105.08-4 -> 580.119.02-1)
[2025-12-19T21:47:37+0100] [ALPM] transaction completed
[2025-12-19T21:47:37+0100] [ALPM] running '20-systemd-sysusers.hook'...
[2025-12-19T21:47:38+0100] [ALPM] running '30-systemd-daemon-reload-system.hook'...
[2025-12-19T21:47:38+0100] [ALPM] running '30-systemd-restart-marked.hook'...
[2025-12-19T21:47:38+0100] [ALPM] running '30-systemd-udev-reload.hook'...
[2025-12-19T21:47:39+0100] [ALPM] running '30-systemd-update.hook'...
[2025-12-19T21:47:39+0100] [ALPM] running '60-depmod.hook'...
[2025-12-19T21:47:42+0100] [ALPM] running '90-mkinitcpio-install.hook'...
[2025-12-19T21:47:42+0100] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'default'
[2025-12-19T21:47:42+0100] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2025-12-19T21:47:42+0100] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64.img
[2025-12-19T21:47:42+0100] [ALPM-SCRIPTLET] ==> Starting build: '6.12.62-1-MANJARO'
[2025-12-19T21:47:42+0100] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2025-12-19T21:47:43+0100] [ALPM-SCRIPTLET]   -> Running build hook: [systemd]
[2025-12-19T21:47:43+0100] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2025-12-19T21:47:44+0100] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2025-12-19T21:47:44+0100] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2025-12-19T21:47:44+0100] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2025-12-19T21:47:46+0100] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2025-12-19T21:47:46+0100] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2025-12-19T21:47:46+0100] [ALPM-SCRIPTLET]   -> Running build hook: [sd-vconsole]
[2025-12-19T21:47:46+0100] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64.img'
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux617.preset: 'default'
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-6.17-x86_64 -g /boot/initramfs-6.17-x86_64.img
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET] ==> Starting build: '6.17.12-1-MANJARO'
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2025-12-19T21:47:47+0100] [ALPM-SCRIPTLET]   -> Running build hook: [systemd]
[2025-12-19T21:47:48+0100] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2025-12-19T21:47:48+0100] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2025-12-19T21:47:48+0100] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2025-12-19T21:47:48+0100] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET]   -> Running build hook: [sd-vconsole]
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.17-x86_64.img'
[2025-12-19T21:47:52+0100] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2025-12-19T21:47:53+0100] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2025-12-19T21:47:53+0100] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux618.preset: 'default'
[2025-12-19T21:47:53+0100] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2025-12-19T21:47:53+0100] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-6.18-x86_64 -g /boot/initramfs-6.18-x86_64.img
[2025-12-19T21:47:53+0100] [ALPM-SCRIPTLET] ==> Starting build: '6.18.1-1-MANJARO'
[2025-12-19T21:47:53+0100] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2025-12-19T21:47:53+0100] [ALPM-SCRIPTLET]   -> Running build hook: [systemd]
[2025-12-19T21:47:54+0100] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2025-12-19T21:47:54+0100] [ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[2025-12-19T21:47:54+0100] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2025-12-19T21:47:54+0100] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2025-12-19T21:47:57+0100] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2025-12-19T21:47:57+0100] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2025-12-19T21:47:57+0100] [ALPM-SCRIPTLET]   -> Running build hook: [sd-vconsole]
[2025-12-19T21:47:57+0100] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2025-12-19T21:47:58+0100] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2025-12-19T21:47:58+0100] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2025-12-19T21:47:58+0100] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2025-12-19T21:47:58+0100] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.18-x86_64.img'
[2025-12-19T21:47:58+0100] [ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[2025-12-19T21:47:58+0100] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2025-12-19T21:47:58+0100] [ALPM] running '99-update-grub.hook'...
[2025-12-19T21:47:59+0100] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-6.18-x86_64
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.18-x86_64.img
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-6.17-x86_64
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.17-x86_64.img
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-6.12-x86_64
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Warning: os-prober will be executed to detect other bootable partitions.
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Its output will be used to detect bootable binaries on them and create new boot entries.
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Found Windows Boot Manager on /dev/nvme1n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Adding boot menu entry for UEFI Firmware Settings ...
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2025-12-19T21:48:00+0100] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme1n1.
[2025-12-19T21:48:01+0100] [ALPM-SCRIPTLET] done
[2025-12-19T21:48:01+0100] [ALPM] running 'dbus-reload.hook'...
[2025-12-19T21:48:01+0100] [ALPM] running 'glib-compile-schemas.hook'...
[2025-12-19T21:48:01+0100] [ALPM] running 'gtk-update-icon-cache.hook'...
[2025-12-19T21:48:01+0100] [ALPM] running 'nvidia-ctk-cdi.hook'...
[2025-12-19T21:48:01+0100] [ALPM-SCRIPTLET] WARNING: updating nvidia-utils version (580.105.08 -> 580.119.02) in /etc/cdi/nvidia.yaml using plain string substitution.
[2025-12-19T21:48:01+0100] [ALPM-SCRIPTLET]  -> If you meet problems, run the following command to regenerate the CDI file:
[2025-12-19T21:48:01+0100] [ALPM-SCRIPTLET]     nvidia-ctk cdi generate --output="/etc/cdi/nvidia.yaml"
[2025-12-19T21:48:01+0100] [ALPM] running 'update-desktop-database.hook'...

After rebooting the ollama container fails to start with

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: failed to fulfil mount request: open /usr/lib/libnvidia-egl-wayland.so.1.1.20: no such file or directory

which seems to be caused by upgraded egl-wayland (4:1.1.20-1 → 4:1.1.21-0)

After quite some digging I found that the /etc/cdi/nvidia.yaml was out of date which I could solve by

sudo nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
sudo systemctl restart docker
2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.