It isn’t. It’s architecture changes pretty significantly with each version, which is annoying when you need it to be stable. It’s also dominated by Redhat, which is a legit concern since they’ll likely start paywalling capabilities eventually.
It isn’t. It’s architecture changes pretty significantly with each version, which is annoying when you need it to be stable. It’s also dominated by Redhat, which is a legit concern since they’ll likely start paywalling capabilities eventually.
Every complaint here is PEBKAC.
It’s a legit argument that Docker has a stable architecture while podman is still evolving, but that’s how software do. I haven’t seen anything that isn’t backward compatible, or very strongly deprecated with notice.
Complaining about selinux in 2024? Setenforce 0, audit2allow, and get on with it.
Docker doing that while selinux is enforcing is an actual bad thing that you don’t want.
So… you’re afraid of the command that does the thing you’re trying to do?
The actual answer to OP’s question is to look up cognitive biases, and to eventually realize that “black” isn’t the relevant descriptor here.
Like seriously and I’m not even intending to be racist
(Though some smarmy asshole will for sure post this unironically thinking that they’re not being racist.)
FSD option costs $199 per month
Doesn’t matter how well it performs, this guarantees I’d never, ever use it.
Gatorz are tough as hell, and have some of the best polarized optics I’ve ever worn.
They’ll do lens replacements, and can make prescriptions as well.
Careful leaving them on a car dashboard though. They’re aluminum frames and I burned my temples once.
Google the concept of an escrow service.
Your edit is a bad take. It doesn’t matter if he’s also selling shirts with MLK and Ghandi quotes. Nazi shit is Nazi shit. Doing Nazi shit, no matter what his own stupid rationalization, makes literally everything else he does irrelevant.
I’m surprised no one’s mentioned the security implications. Mounting with nosuid and nodev options can undermine rootkit or privileged escalation exploits.
deleted by creator
deleted by creator
deleted by creator
Flatpak is itself a file manager.
That duplicate of your folder in /run is due to filesystem links (or more likely a fuse mount, I’ve never actually looked into how flatpak works). But either way, they aren’t copies of the data.
Free tier is super limited and super easy to accidentally break out of. I had a single file in S3, but because my logging settings were wrong, I broke the free tier with junk logs.
The t2 micro ec2 instances are fine, but you need to be very careful about their storage and network egress.
Best use I’ve had for AWS that has managed to stay within the free limits has been Lambda. Managed to convert a couple self hosted discord bots to a few Lambda functions, works great. Plugging it into CloudFormation and tying up CI/CD with CodePipeline and the like were overkill but good learning exp.
I don’t think there’s any ECS free tier, but you can fit a private container repository in the free S3 limits as well.
deleted by creator
Don’t “declutter” manually. Use your package manager.
You’re going to want to look up things like symlinks, hard links, fuse filesystems, and bind mounts among other concepts. Your “whole directory” and other duplicates are artifacts of how the filesystem and process management works, and simply running fsearch or find over them is going to be confusing if you don’t know what you’re looking at.
One Unix concept that carries over to Linux is that everything is a file. Your shared memory space, process data, device driver interfaces, etc, all of it is accessible somewhere in the same virtual filesystem tree as the actual files.
Because of this, there’s very little reason to have the whole filesystem indexed from root. If you’re worried about space usage, you want to work with packages through the package manager. If you’re worried about system integrity, you’ll want package validators.
The above is accurate, and can be considered accurate for any directory below or at well.
Per /run, it’s also mounted in memory, so trying to “declutter” it won’t get you anywhere and things will return on reboot.
Just cause you’ve never seen them doesn’t make it not true.
Try using quadlet and a .container file on current Debian stable. It doesn’t work. Architecture changed, quadlet is now recommended.
Try setting device permissions in the container after updating to Debian testing. Also doesn’t work the same way. Architecture changed.
Redhat hasn’t ruined it yet, but Ansible should provide a pretty good idea of the potential trajectory.