falcon15500

joined 1 year ago

Last time I completely re-flashed my phone and only loaded it up with some "travel" accounts that were very basic. It was quite a lot of hassle, though.

This time I think I will just sign out of and delete any cloud services/accounts of concern (including my password safe) from the phone. I will sanitise it of anything I don't want getting into anothers hands.

Once I am safely across the border I can re-download/install what I need.

 

Hi all,

I am travelling soon to the US, for my vocation and as a long-time private person I will be taking some steps to maintain my privacy as I enter the country.

As this is an interesting area of the topic, I have decided to throw the question open to all of you.

What precautions (IT, physical, mental, otherwise) do you undertake when travelling internationally?

M.

[–] falcon15500@lemmy.nine-hells.net 4 points 8 months ago (1 children)

Why do you think that google, Microsoft and Amazon never got into the infrastructure business before?

Amazon was in the infrastructure business well before containers were the "big thing".

Podman rootless, using quadlets for systemd services. :D

[–] falcon15500@lemmy.nine-hells.net 11 points 8 months ago* (last edited 8 months ago) (4 children)

Check out the following link - I am pretty sure its what I used to get it all working.

https://3os.org/infrastructure/proxmox/gpu-passthrough/igpu-passthrough-to-vm/

leader of the free world

Pffft.

[–] falcon15500@lemmy.nine-hells.net 2 points 9 months ago* (last edited 9 months ago)

Hey, sorry for the late reply. I am running rootless using a dedicated user, so I use systemctl --user to control the container. From what I understand, when running rootless the root user inside the container correlates to the outside user (which is running the container), in terms of permissions. The external directories I bind mount into the container as externally owned by my dedicated user, so that the root user inside the container owns them (inside the container).

[–] falcon15500@lemmy.nine-hells.net 2 points 10 months ago (2 children)

Are you doing rootless or rootfull podman? I am doing rootless and I have the following in my radarr container - PUID=0 PGID=0

[–] falcon15500@lemmy.nine-hells.net 2 points 10 months ago (1 children)

I am using Calibre-Web mostly - but I have run into issues with thumbnail generation after my collection hit around 500000 books. I am just over 600000 now, but a large swathe don't have thumbnails unless I do a manual metadata search. I should probably look for an alternative, but at this point I CBF.

[–] falcon15500@lemmy.nine-hells.net 6 points 10 months ago (1 children)

binhex/arch-qbittorrentvpn

Yeah it looks pretty slick but not so much slicker than Frigate that I will pay to be in the beta. :)

 

I am going to sit for the RHEL 9 version of the ex294 exam soon. Does anyone have any general exam tips for the ex294? If anyone has sat for the RHEL 9 version, care to share (within bounds of the NDA) any insights?

 

cross-posted from: https://lemmy.nine-hells.net/post/56646

Hi all - recently moved my old docker setup across to Podman rootless containers, however I am having some trouble with getting my Plex container to use the on CPU hardware transcoding.

"/dev/dri" device is being passed into the container and after reading, I also added "--group-add=keep-groups" to my configuration.

Still no luck getting the "video" group to the plex user inside the container so it can access the device.

Anyone successfully running rootless Plex with H/W transcode?

 

Hi all - recently moved my old docker setup across to Podman rootless containers, however I am having some trouble with getting my Plex container to use the on CPU hardware transcoding.

"/dev/dri" device is being passed into the container and after reading, I also added "--group-add=keep-groups" to my configuration.

Still no luck getting the "video" group to the plex user inside the container so it can access the device.

Anyone successfully running rootless Plex with H/W transcode?

view more: next ›