non_burglar @ non_burglar @lemmy.world

Posts

0

Comments

334

Joined

2 yr. ago

Yes, of course. Those things are also all true.

Currently still fixing alpine Linux lxc running docker that decided to stop being able to network after a PVR update.

I've managed to migrate my services to debian-based docker Lxc, but it bothers me that I can't figure this out.

Best I have so far is that flushing the iptables in alpine lxc works temporarily.

I agree, but we should have diversified our trade in the 90s when we realized Mulroney's us/can free trade agreement wasn't going to last forever, and when it was becoming obvious that China was rising fast as a manufacturing powerhouse.

IMO, we should have forged a tightly integrated trade agreement with the EU and spearheaded the Trans Pacific Partnership way sooner.

We're in the pickle of current events because we were largely complacent at the table of a global market that marched ahead without us in the ways we wanted.

How efficient is using a GPU? I understood the efficiency wasn't nearly as good, but that may have been info from a while back.

It's well worth it to get a $50 coral tpu for object detection. Fast inference speed and nearly zero CPU usage.

Keys spread out? I don't understand...

I appreciate the reply, but I guess I wasn't clear on what I was asking.

It's obvious who this is for in the literal sense, what I mean is: what is the use case for this?

On the homelab front, I don't see enough need to unify my GUI access, and i have roughly 30 containers to manage. At that point, most homelab admins gravitate to automation.

On the professional front, I can tell you that unifying the keys to mgmt interfaces to critical infrastructure in a single app is not a welcome tool to see on my junior admin desktops. And if it's simply the interface to mgmt portals without storing keys, then I would have my doubts about a junior admin who hasn't developed a personal strategy to manage this themselves.

Don't get me wrong, I'm happy to encourage you to develop this, but the second you write "trying to make a living from this", you should know that these questions are coming.

If I were across the table from you trying to understand what you're selling me, I would want to know:

• how do you handle secrets in transit and at rest?
• can I deploy this once and set access for various departments or employees?
• can I find out who has been using the tool?
• how does the app handle updates?

You can see where this is going. If I buy this tool for use by several people, I don't want to have to wrap it in vault entries and update scripts just to meet compliance with my client's environment.

What is your target audience for this? I'm having trouble understanding who this product is for.

Sounds reasonable, and I'm sure you're on your way to solving this.

In my experience thinking hard about my storage needs, I've found that as long as I can get decent performance and a bit of redundancy, a solid and tested backup plan can fill in the rest in terms of data safety and integrity.

"Which goes to show that being a bum knows no gender."

Your focus shouldn't be on what technologies to use, because you can't know what will help until you know what you're trying to do.

Define your use case and the problems you can see now, and the technologies to address them will become more apparent.

Please draw from the context of this thread that I mean future deaths.

You're lost in the semantics. Outcomes like fewer deaths resulting from foreign policy decisions, including belligerent invasions, matter more than perceived political "moral" calculus.

I did. It's a culture vulture article, you just need to use an incognito tab.

As unpleasant as the content is, just read the article. And remember that lots of folks have trusted Neil Gaiman for a long time (I'm 50) to tell stories they connect with, especially in the 90s when there were fewer writers to do so.

sombre reflection

You apparently still haven't read the article. Given the reactions to your comment, you may want to go see why the comments are "sombre", as you put it.

Problem with Poettering is that he was right, but he was a dick about it. Like Rick Sanchez.

No clue what he did (have not yet read the article). Haven’t really consumed any of his media.

I’m surprised everyone else is surprised

This comment didn't need to be made.

You really, really should use this as an example for yourself in the future to read the room. That means read the article before making a thoughtless comment on something you obviously didn't fully grasp.

Pen danger to the eye is obvious to most people. Cancer caused by a lifetime of drinking is not.

I'm trying to indicate that docker has its own kinds of problems that don't really occur for software that isn't containerized.

I used the immich issue because it was actually NOT indicated as a breaking change by the devs, and the few of us who had migrated the same compose yml from older veraions and had a problem were met with "oh, that is a very old config, you should be using the modern one".

Docker is great, but it comes with some specific understanding that isn't necessarily obvious.

For one, if the compose file syntax or structure and options changes (like it did recently for immich), you have to dig through github issues to find that out and re-create the compose with little guidance.

Not docker's fault specifically, but it's becoming an issue with more and more software issued as a docker image. Docker democratizes software, but we pay the price in losing perspective on what is good dev practice.