home/kubernetes-deployments
2
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Compare commits

base: home:c6028dc46e47eb46cbf525a1db477609f4d43b31
Branches Tags
home:master
..
compare: home:3e28f0f3e3776d2515f953636d2fa5a3e5cb7c51
Branches Tags
home:master

No commits in common. "c6028dc46e47eb46cbf525a1db477609f4d43b31" and "3e28f0f3e3776d2515f953636d2fa5a3e5cb7c51" have entirely different histories.
c6028dc46e ... 3e28f0f3e3

2 changed files with 1 additions and 15 deletions
Show stats Expand all files Collapse all files

14
docs/longhorn.md
View file

@ -1,19 +1,5 @@
# Longhorn notes # Longhorn notes
## Troubleshooting
```
Multi-Attach error for volume "prowlarr" Volume is already exclusively attached to one node and can't be attached to another
```
I solved the above problem like this:
```
❯ kubectl get volumeattachments | grep prowlarr
csi-f13ee1f46a4acc0d7e4abe8a3c993c7e043e9a55cd7573bda3499085654b493a driver.longhorn.io prowlarr lewis true 3m38s
❯ kubectl delete volumeattachments csi-f13ee1f46a4acc0d7e4abe8a3c993c7e043e9a55cd7573bda3499085654b493a
❯ kubectl rollout restart -n media deployment prowlarr
```
## Migration from NFS to Longhorn ## Migration from NFS to Longhorn
1. Delete the workload, and delete the PVC and PVC using NFS. 1. Delete the workload, and delete the PVC and PVC using NFS.

2
globals.nix
View file

@ -5,7 +5,7 @@
deluge = "linuxserver/deluge:2.1.1"; deluge = "linuxserver/deluge:2.1.1";
jellyseerr = "fallenbagel/jellyseerr:2.1.0"; jellyseerr = "fallenbagel/jellyseerr:2.1.0";
radarr = "lscr.io/linuxserver/radarr:5.15.1"; radarr = "lscr.io/linuxserver/radarr:5.15.1";
prowlarr = "lscr.io/linuxserver/prowlarr:1.27.0"; prowlarr = "lscr.io/linuxserver/prowlarr:1.26.1";
sonarr = "lscr.io/linuxserver/sonarr:4.0.11"; sonarr = "lscr.io/linuxserver/sonarr:4.0.11";
bazarr = "lscr.io/linuxserver/bazarr:1.4.5"; bazarr = "lscr.io/linuxserver/bazarr:1.4.5";
atuin = "ghcr.io/atuinsh/atuin:18.3.0"; atuin = "ghcr.io/atuinsh/atuin:18.3.0";