[-] glizzyguzzler 2 points 23 hours ago

Odd, I’ll try to deploy this when I can and see!

I’ve never had a problem with a volume being on the host system, except with user permissions messed up. But if you haven’t given it a user parameter it’s running as root and shouldn’t have a problem. So I’ll see sometime and get back to you!

[-] glizzyguzzler 2 points 2 days ago

That’s pretty damn clever

[-] glizzyguzzler 4 points 3 days ago* (last edited 2 days ago)

I try to slap anything I’d face the Internet with with the read_only to further restrict exploit possibilities, would be abs great if you could make it work! I just follow all reqs on the security cheat sheet, with read_only being one of them: https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html

With how simple it is I guessed that running as a userand restricting cap_drop: all wouldn’t be a problem.

For read_only many containers just need tmpfs: /tmp in addition to the volume for the db. I think many containers just try to contain temporary file writing to one directory to make applying read_only easier.

So again, I’d abs use it with read_only when you get the time to tune it!!

[-] glizzyguzzler 5 points 3 days ago

Looks awesome and very efficient, does it also run with read_only: true (with a db volume provided, of course!)? Many containers just need a /tmp, but not always

[-] glizzyguzzler 1 points 3 days ago* (last edited 3 days ago)

I trust the check restic -r '/path/to/repo' --cache-dir '/path/to/cache' check --read-data-subset=2000M --password-file '/path/to/passfile' --verbose. The --read-data-subset also does the structural integrity while also checking an amount of data. If I had more bandwidth, I'd check more.

When I set up a new repo, I restore some stuff to make sure it's there with restic -r '/path/to/repo' --cache-dir '/path/to/cache' --password-file '/path/to/passfile' restore latest --target /tmp/restored --include '/some/folder/with/stuff'.

You could automate that and make sure some essential-but-not-often-changing files match regularly by restoring them and comparing them. I would do that if I wasn't lazy I guess, just to make sure I'm not missing some key-but-slowly-changing files. Slowly/not often changing because a diff would fail if the file changes hourly and you backup daily, etc.

Or you could do as others have suggested and mount it locally and just traverse it to make sure some key stuff works and is there sudo mkdir -p '/mnt/restic'; sudo restic -r '/path/to/repo' --cache-dir '/path/to/cache' --password-file '/path/to/passfile' mount '/mnt/restic'.

[-] glizzyguzzler 4 points 3 days ago

I have my router (opnsense) redirect all DNS requests to pihole/adguardhome. AdGuard home is easier for this since you can have it redirect wildcard *.local.domain while pihole wants every single one individually (uptime.local.domain, dockage.local.domain). With that combo of router not letting DNS out to upstream servers and my local DNS servers set up to redirect *.local.domain to the correct location(s), my DNS requests inside my local network never get out where an upstream DNS can tell you to kick rocks.

I combined the above with a (hella cheap for 10yr) paid domain, wildcard certified the domain without exposure to the wan (no ip recorded, but accepted by devices), and have all *.local.domain requests redirect to a single server caddy instance that does the final redirecting to specific services.

I’m not fully sure what you’ve got cooking but I hope typing out what works for me can help you figure it out on your end! Basically the router doesn’t let anything DNS get by to be fucked with by the ISP.

214
Duality of humankind rule (files.catbox.moe)
submitted 2 weeks ago by glizzyguzzler to c/onehundredninetysix
276
submitted 3 weeks ago by glizzyguzzler to c/onehundredninetysix
115
rule (files.catbox.moe)
submitted 3 weeks ago by glizzyguzzler to c/onehundredninetysix
34
submitted 3 weeks ago by glizzyguzzler to c/selfhosted@lemmy.world

I have a bridge device set up with systemd, br0, that replaces my primary ethernet eth0. With the br0 bridge device, Incus is able to create containers/VMs that have unique MAC addresses that are then assigned IP addresses by my DHCP server. (sudo incus profile device add <profileName> eth0 nic nictype=bridged parent=br0) Additionally, the containers/VMs can directly contact the host, unlike with MACVLAN.

With Docker, I can't see a way to get the same feature-set with their options. I have MACVLAN working, but it is even shoddier than the Incus implementation as it can't do DHCP without a poorly-maintained plugin. And the host cannot contact the container due to the MACVLAN method (precludes running a container like a DNS server that the host server would want to rely on).

Is there a way I've missed with the bridge driver to specify a specific parent device? Can I make another bridge device off of br0 and bind to that one host-like? Searching really fell apart when I got to this point.

Also, if someone knows how to match Incus' networking capability with Podman, I would love to hear that. I'm eyeing trying to move to Podman Quadlets (with Debian 13) after I've got myself well-versed with Docker (and its vast support infrastructure to learn from).

Hoping someone has solved this and wants to share their powers. I can always put a Docker/podman inside of an Incus container, but I'd like to avoid onioning if possible.

71
butts rule (files.catbox.moe)
submitted 1 month ago by glizzyguzzler to c/onehundredninetysix
103
rule (files.catbox.moe)
submitted 1 month ago by glizzyguzzler to c/onehundredninetysix
356
tithe rule (files.catbox.moe)
submitted 1 month ago by glizzyguzzler to c/onehundredninetysix
165
praxis rule (files.catbox.moe)
submitted 2 months ago by glizzyguzzler to c/onehundredninetysix
385
rule (files.catbox.moe)
submitted 2 months ago by glizzyguzzler to c/onehundredninetysix
171
who is Sandy Loam rule (files.catbox.moe)
submitted 2 months ago by glizzyguzzler to c/onehundredninetysix
24
submitted 2 months ago by glizzyguzzler to c/onehundredninetysix

Context is:

  • I was luckily banned from the fallen onehundredninetysix for vehemently rejecting the orchestrated hoodwinking

  • luckily banned because i'd have posted boston's sloppiest there like three times before it properly made it to the people's onehundredninetysix

  • I use the default web UI which is aggressively broken on my old phone like the pleb I am

95
🤤🤤rule (files.catbox.moe)
submitted 2 months ago by glizzyguzzler to c/onehundredninetysix
[-] glizzyguzzler 75 points 4 months ago* (last edited 4 months ago)
[-] glizzyguzzler 115 points 5 months ago

First date fit includes underwear??

[-] glizzyguzzler 127 points 8 months ago

Ah, I see I am in the presence of a preeminent N64 titty connoisseur

[-] glizzyguzzler 67 points 1 year ago

The whole joke plays into a terminally horny me-me emoji copypasta that people liked to crank out a few years ago - making it “moldy”! The point is the emojis! Here’s one for dickmas that takes it to 11:

MERRY🎅COCKMAS🍆🍆🍆🍆😜😜😜🐓🐓🐓🐓 AND HAPPY 😁 HOE-LIDAYS 😲😲😲😩😩😩 MERRY🎅COCKMAS🍆🍆🍆🍆😜😜😜🐓🐓🐓🐓 AND HAPPY 😁 HOE-LIDAYS 😲😲😲😩😩😩 THIS YEAR 📆 I'M DEFINITELY ✅ ON THE 😈😈😈NAUGHTY😈😈😈LIST📜📝 BECAUSE I'M 👈A GIGANTIC 🏳‍🌈🌈🏳‍🌈🌈🏳‍🌈🌈🏳‍🌈🌈🎄❄HO-HO-HOMOSEXUAL❄🎄🏳‍🌈🌈🏳‍🌈🌈🏳‍🌈🌈🏳‍🌈🌈 WHICH IS NOT 🙅‍♀️❌ VERY CHRISTIAN ⛪🙏 BUT I STILL CAN APPRECIATE 😜 SAINT DICK ✨🎉✨🎉 I CAN'T WAIT FOR 🎅SANTA🎅 TO SLIDE DOWN MY CHIMNEY ⬇🏠😜💦 AND STUFF MY STOCKING 🧦🎁😜 FULL OF DILDOS 😱🍆 AND PENIS PARAPHERNALIA 🍆🍆🍆🍆💦💦💦 BECAUSE I'M JUST A LITTLE 🤏 FESTIVE 🎄🎅🤶⛄❄🎁FAGGOT🏳‍🌈🌈🏳‍🌈🌈🍆🍆😜😜😩😩😩💦💦💦

SO TO ALL MY 💋👄💋👄💋SLUTTY 😩😩😩💋💋💋 SANTA'S 🎅🎅🏿🎅🏽🎅🏻 LITTLE HELPERS 😉😉😉👏👏& HORNY 😩😈 CHRISTMAS ELVES ��🏻‍♂️🧝🏻‍♂️🧝🏻‍♂️ REMEMBER LET IT "SNOW" 🌨🌨🌨❄❄❄❄⛄⛄⛄😜😜😜😜😜💦💦💦💦 AND DON'T FORGET TO 🌟✨🌟✨DECORATE✨🌟✨🌟 YOUR "TREE" 😜😜😜🎄🎄🎄🎄🎄🍆🍆🍆🍆🍆 I'LL BE WAITING 🕚🕕🕠 UNDER THE MISTLETOE 🍃🦶 WRAPPED UP IN RIBBON 😳🎁🎀💝 WAITING ⏱ FOR YOU 👆TO UNWRAP 😳🎀 ME SO WE CAN TASTE 👅💦 EACHOTHER'S CANDY CANES 🍬✨🍬✨🍬✨😩😩😩🍆🍆🍆💦💦💦

[-] glizzyguzzler 67 points 1 year ago

I’d guzzle

view more: next ›

glizzyguzzler

joined 2 years ago