Posts by llaumgui

  • containerd.io upgrade screws with Portainer

    I have upgraded my server and all is fine with the :

    Code
    systemctl show docker.service | grep MIN
Environment=DOCKER_MIN_API_VERSION=1.24

    I use :

    • Portainer: direct access to socket.
    • linuxserver/socket-proxy: direct access to socket.
    • traefik: access socket over proxy.
    • nickfedor/watchtower: direct access to socket. (because upgrade to socket cause crash).
    • cadvisor: direct access to socket.
    • homepage : access socket over proxy.

  • containerd.io upgrade screws with Portainer

    Quote from DjoeC

    Another solution from here: https://gathering.tweakers.net…message/83909852#83909852

    Code
    systemctl edit docker.service
Add this part above the line ### Lines below this comment will be discarded:
[Service]
Environment=DOCKER_MIN_API_VERSION=1.24
Save the file and exit
systemctl restart docker

    Works for Portainer only or all other containers that use the API ? I use socket on Portainer, docker-socket-proxy, watchtower and cAdvisor.

  • NFS crash

    OK, effectively, just before, I have a huge load...


    Before :

    Code
    sysctl -a | grep dirty | grep ratio     
vm.dirty_background_ratio = 1
vm.dirty_ratio = 20

    After :

    Code
    sysctl -a | grep "dirty" | grep ratio     
vm.dirty_background_ratio = 5
vm.dirty_ratio = 10

  • NFS crash

    I have this. And I use NFS v4 only (Debian 10 and Fedora 40 client).

  • NFS crash

    Hi,



    since several weeks, I observe NFS cashes. My mount is broken, I can't stop nfs-kernel-server, I can't restart it, the only solution is to reboot my server. I have read that NFS was updated recently, but I can't find any procedure to fix my issue.

  • Somes issues in journalctl (DP dual mode and NAK bailout)

    OK ! Thanks, with 6.2 / 6.5 I haven't any drivers issues... Buts I have docker issues... I can't use docker, I have a lot of containers that crash :


    Code
    could not create Unix-domain socket in directory "/var/run/postgresql"


    Code
    Failed to create UnixStream

    Is there some adaptation to make docker working with pve kernel ?

  • Somes issues in journalctl (DP dual mode and NAK bailout)

    Hi,


    I just migrate from OMV6 to 7, and I see a lot of error in journalctl :


    Code
    Mar 31 09:28:13 deepspace9 kernel: i2c i2c-4: sendbytes: NAK bailout.
Mar 31 09:28:13 deepspace9 kernel: i2c i2c-4: sendbytes: NAK bailout.
Mar 31 09:28:14 deepspace9 kernel: i2c i2c-4: sendbytes: NAK bailout.
Mar 31 09:28:14 deepspace9 kernel: i2c i2c-4: sendbytes: NAK bailout.
Mar 31 09:28:14 deepspace9 kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 7f

    These errors are also present in OMV6, but just don't check before (it's a recent installation). I have a N100 NAS and I think it's a display issue. IS there a way to stop this message every minute ?


    Some information:


    Code
    root@deepspace9 /home/llaumgui> lspci -k | grep -EA3 'VGA|3D|Display' 
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [UHD Graphics]
    Subsystem: ASRock Incorporation Alder Lake-N [UHD Graphics]
    Kernel driver in use: i915
    Kernel modules: i915
root@deepspace9 /home/llaumgui> dpkg --list | grep intel
ii  whois                              5.5.17                              amd64        intelligent WHOIS client

    should I install drivers like intel-media-va-driver ?

  • [mountpoint] <defunct> with monit and NFS

    Hi,


    in OMV5, I have 3 zombies:

    Code
    root     11614  0.0  0.0      0     0 ?        Zs   11:52   0:00 [mountpoint] <defunct>
root     11615  0.0  0.0      0     0 ?        Zs   11:52   0:00 [mountpoint] <defunct>
root     11616  0.0  0.0      0     0 ?        Zs   11:52   0:00 [mountpoint] <defunct>


    service monit stop remove zombies but zombies is here after monit start... I have 3 NFS mount, for me it's a error between NFS mount and monit. Any resolution ?

  • Portainer on OMV4

    Hi,



    I would like prepare the migration from OMV4 to OMV5. I have migrate all unsupported plugins to Docker but now I would like migrate to Portainer before migrate to OMV5. The goal of that is to have a full compliant OMV5 system before migrating. Is there a way to install Portainer in OMV4 ?


    When I update my installation to OMV5, my containers keep running ? I will just loose admin pannel and I can migrate to Portainer after ? Container by container ?