Lifebandit666

joined 1 year ago
[–] [email protected] 24 points 3 months ago (3 children)

I went to a crypt in Britain as a kid, can't remember where tf it was, but I still remember it because it was super interesting.

It's where I learned about Trepanning and how they did it back in olden times to "let the bad spirits out" and it actually worked because it reduced swelling around the brain by giving the blood a way out.

[–] [email protected] 2 points 3 months ago (1 children)

I've stroked a Capybara

[–] [email protected] 7 points 4 months ago (1 children)

This isn't real life it's an online forum in a video game

[–] [email protected] 6 points 4 months ago

"Dodgy Firestick"

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 children)

You need to pick a machine (if you only have 1 you don't lol) to be your web portal, bang a block of code in via ssh or command line (I copy pasted) then you can access Portainer via the web portal.

From there "Stacks" is Docker Compose and you can fiddle with your containers, networking settings and all the other stuff via a UI instead of having to SSH in all the time to look at your compose files.

Then if you wanna use docker on more machines you just bang a block of code into that machine via ssh and it will appear in your Portainer

Far easier imho

[–] [email protected] 2 points 4 months ago (3 children)

I found a lot of the problems I had with Docker were with Docker. Once I moved to using Portainer for Docker it became much more accessible.

[–] [email protected] 2 points 4 months ago

This looks like a good shout. I have actually tried it out but it was years ago when I was trying to get a Sonos-like service and ultimately settled on Squeezebox.

Maybe it's time to try it again, thanks for the idea

[–] [email protected] 3 points 4 months ago

It's a Dell Optiplex 7050

[–] [email protected] 2 points 4 months ago

Try a live Proxmox USB, it's what I did when my machine went unresponsive. Allowed me to look through the logs of the OS when it hadn't booted to find out what went wrong.

For me it was that I had put my USB HDDs in via Fstab and one had died, which made Proxmox unbootable until I hashtagged the lines out in fstab.

[–] [email protected] 4 points 4 months ago* (last edited 4 months ago) (2 children)

Eh I did all this with a cheap thin client.

Proxmox as the frontend

OMV in a VM with usb passed through

Debian VM for Plex and Docker

Adguard and Nginx and Arr in Docker

Network sharing from the OMV VM

HDDs to USB.

[–] [email protected] 7 points 4 months ago* (last edited 4 months ago) (2 children)

I've solved this exact issue and numerous others with samba / CIFS recently. This is how I have my Proxmox on a mini pc with usb mounted HDDs at present:

1 VM Home Assistant OS, not relevant really

1 VM OMV Open Media Vault.

1 VM Debian with Docker installed.

So in my experience over the last few months you want your usb drive to have absolutely nothing to do with Proxmox. Nope.

I had 3 hooked in mounted in Proxmox and when one of them threw a fit Proxmox refused to load.

Better to have a NAS VM installed and have the drive(s, I have 3, 2x1tb and 1x750gb) passed straight through, whole usb, to the NAS VM.

This means if the drive fails Proxmox doesn't break, and also in my experience with OMV, it'll still run if a drive breaks

Then what I did was set up the shares and made them samba in OMV then set my other VM, the Debian one, with mount points in the Fstab.

The key for me in this endeavour was to make sure the Fstab entry made sure that the OS wouldn't fail if it couldn't find a drive, as happened in Proxmox, so I made sure "nofail" was somewhere in the Fstab config.

For Samba to work in Linux you need to install cifs-utils, then add a line in /etc/fstab. Mine goes:

//omv.local/sharename /mnt/filename cifs credentials=/etc/cifs-credentials,file_mode=0777,dir-mode=0777,auto,nofail,vers=3.0 0 0

You have to create the mount point mkdir /mnt/filename and give it permissions with chmod

You also need to made the cifs-credentials file in /etc/

It needs to contain:

username=yourusername password=yourpassword domain=WORKGROUP

Then what I do for Audiobookshelf and whatnot is mount the mount point as directories in Portainer under the volumes: - /mnt/Downloads:/Downloads

Then in the UI of the service I'm using in Docker I can use the Downloads folder and it's the mount point.

This is what's working well for me. If a drive fails I try and fix it in OMV instead of trying to plug a monitor into my mini pc to try and work out from the logs why Proxmox has failed...

Use this comment as a framework for your research and save yourself some heartache. You can mount the CIFS/Samba share to Proxmox and use that, so you can still use the drive in Proxmox for backups and such

[–] [email protected] 1 points 4 months ago

I've just come back to this comment to get sabnzbd running, thanks again

view more: ‹ prev next ›