digity

Is there a way to write history immediately instead of waiting until logout/exit?? I often have multiple SSH sessions open simultaneously and don't really exit/logout on each (remote client restarts or something), but want all their history.

I'm in the middle of upgrading my cache pool size and adding more drives to the main array. After Mover moved appdata and system to the storage array and the outgoing cache pool was removed I took the liberty of applying any available updates and upgrades to any community plug-ins and Unraid's Docker engine. Mover moved appdata and system to the new cache pool when it was created. The problem is it seems Unraid's Docker installation got screwy during the upgrades because now when trying to start the containers I get the errors below (all via docker-compose, I don't use Unraid's web based Docker manager - this all worked beautifully before). How do I perform a factory reset/fresh start of Unraid's Docker installation? If that's not the best way to resolve the issues, please advise how. Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/docker-entrypoint.sh": stat /docker-entrypoint.sh: no such file or directory: unknown => [internal] load build definition from Dockerfile => => transferring dockerfile: 32B => [internal] load .dockerignore => => transferring context: 2B => [internal] load metadata for docker.io/library/alpine:latest => CACHED [1/4] FROM docker.io/library/alpine:latest@sha256:65a2763f593ae85fab3b5406dc9e80f744ec5b449f269b699b5efd37a07ad32e => [internal] load build context => => transferring context: 134B => ERROR [2/4] RUN echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org/alpine/edge/community/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org ------ > [2/4] RUN echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org/alpine/edge/community/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org/alpine/" >> /etc/apk/repositories && apk add --no-cache bash transmission-cli inotify-tools: #0 0.545 container_linux.go:367: starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory ------ failed to solve: executor failed running [/bin/sh -c echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing/" >> /etc/apk/repositories && echo "http://dl-cdn.alpinelinux.org/alpine/edge/community/" >> /etc/apk/repositories && ec/dl-cdn.alpinelinux.org/alpine/edge/main/" >> /etc/apk/repositories && apk add --no-cache bash transmission-cli inotify-tools]: exit code: 1

It's tidier for me to have my homelab modularized, keeping roles/functions separate. Taking down the whole network just to troubleshoot one issue got old very fast for me.

I'm running Unraid 6.9.2 bare metal and it only stores my Plex media files (shared via NFS). I have Plex, etc. running in Docker containers in a Ubuntu Server VM on my ESXi physical server. The Unraid NFS share is mounted in the Ubuntu VM (/etc/fstab syntax below) then passed to the Docker containers via the volume feature. I'm constantly getting "Stale file handle" errors within the containers and the apps can not access the media files and folders. Restarting the VM fixes the problem momentarily (restarting the container by itself does NOT), but the error occurs again soon after. Why is this error occurring and how do I resolve it? /etc/fstab file on Ubuntu Server VM (Docker host): 192.168.0.20:/mnt/user/medialibrary /mnt/medialibrary nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0 P.S. - the NFS mount options in fstab were copied over from my old TrueNAS setup (the media files use to be on a TrueNAS server, Unraid replaced that server)