Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
2
Comments
383
Joined
3 yr. ago

  • I was going to buy the Lego Star Trek enterprise, but it was sold out before I got there. Oh well, they saved me from myself with artificial supply restrictions.

    Instead, I didn't buy anything.

  • There were decorations for sale at Costco in California in late August. Decorative gourd season decorations hadn't even shown up yet.

  • I usually prefer "soggy flesh sack", but I do admit the "meat mech" angle has me intrigued.

  • Oh, and I've found SELinux easier to handle with podman, but that might be just more experience now.

  • Nothing really critical.

    Differences from where I'm at

    • docker doesn't have native systemd integration ("quadlets")
    • docker needs a daemon running
    • podman has pods (like kubernetes) which are great for isolation of complex services
    • you can run podman containers with kubernetes yaml
  • I really wish the bot curated the feed a bit. The number of times I have clicked through to the comments only to find a flagged/removed post because I wanted to enjoy watching the fireworks...

  • First time ever the Winklevoss Twins haven't shared a list entry?

  • Deleted

    Permanently Deleted

    Jump
  • Layers, intentional or not.

    Template:

  • MSNBC hosting a hit piece from a national review columnist. Figures.

  • I see. Yeah, that compose file is gross unless you're running this on a dedicated vps, and even then...

  • Allegedly:

  • Conservatives love the optics of performative witch hunts.

  • Once podman is installed (iirc the network package is marked as a dependency for most package managers) and your user is configured (provide subuids/subguids), I really think podman is a simpler model. The containers you run are actually yours (not root's) and you don't need to be part of a privileged docker group to run them. Of course, you can run containers as root with podman too: just use sudo.

    You'll actually need to configure your user the same way for running docker in rootless mode, which should be the default.

    Your dockerfile will work with podman. Your docker-compose file will too (via podman compose). You'll have access to awesome new capabilities like pods, and defining your containers with kubernetes style yaml, and running your containers via systemd.

    However, with rootless podman/docker, you should remove any/all of the USER silliness the rootful/default docker people do to protect themselves a bit from rogue processes effectively running as root and/or container escapes to root.

  • Tiling WM and Gruvbox. Doesn't get any better!

  • Heck yeah. Nothing like a good sandwich!

    And to anyone who might doubt, the veg is clutch too. From texture, to flavor, to color, it makes the difference between decent and great.