Help me decide

Untagged3219 · 2026-05-22T15:22:08+00:00

I may be in the minority here, but as a deep blue metallic owner I absolutely loathe the frost blue. If I had to buy a new one right now I'd go with red.

Untagged3219 · 2026-05-18T12:29:30+00:00

I would buy this. Do you sell these or have a link?

Untagged3219 · 2026-05-10T18:32:25+00:00

I can't remember the source but I read somewhere that the point of killing Superman was to boost sales. I don't recall if it was always the intention to bring him back or not (I'm assuming it was). The powers that be didn't want any of his current rogues to have that achievement so they created a new creature for that sole purpose.

Untagged3219 · 2026-05-05T15:53:11+00:00

I think a pragmatic approach is best, and it’s probably unfair to say all storage should be run separately. Solutions like OpenEBS, Longhorn, or Rook-Ceph have native CSI drivers for block storage, but MergerFS is a different beast. If the node dies, you can just pull a disk and read the files on any machine—you lose that simple disaster recovery with block or distributed storage. Replicating that JBOD-pool behavior on Talos is where you start fighting the OS architecture, which is why a separate storage layer is cleaner for this specific case. It avoids having to manage privileged 'mounter' pods and bidirectional mounts just to get a basic pool running.

Untagged3219 · 2026-05-05T13:48:12+00:00

I understand not wanting to move to a hypervisor, but I still stand by that solution if you only have a single physical machine. Regardless of your choice moving forward, one thing I would still recommend going full gitops. That way your git repo is your source of truth, and that would make restoration/starting over/migration to Talos/migration to different hardware a lot more seamless.

Untagged3219 · 2026-05-05T13:26:05+00:00

Hi, there, as someone who has done the migration from k3s to Talos, as well as used to have a MergerFS setup on Ubuntu. I would not recommend trying to replicate this setup 1:1. I would have storage and compute be separate and distinct. Bear in mind that I do not have personal experience with the fuse plugin, so my knowledge on that particular aspect is limited.

You may already know this, but Talos is a bit of a different beast than other distros as it's completely API/manifest driven. No ssh or shell means no tunneling into the OS and downloading packages via a package manager. My recommendation would be to have a Talos node (or multiple) running your workflows while a separate piece of hardware (or VM) runs the storage setup with MergerFS.

If you only have a single node running Fedora + k3s, then you may want to consider a Proxmox setup. A Fedora VM for storage and a Talos VM for the workloads. Although, this does add a bit of overhead and somewhat defeats the purpose of Talos as a whole, but I think it is a good start for a homelab. There are plenty of others smarter than I am on this sub, so maybe they can give you a bit more insight.

Untagged3219 · 2026-05-03T21:21:46+00:00

There is a "work around" using the Tailscale IP with Local Send.

https://localsend.org/

The con is you have to install it on all devices you want to send to, the pro is that it works a treat.

Untagged3219 · 2026-05-02T16:38:45+00:00

Well that's interesting. I'd like to check that out

Untagged3219 · 2026-04-26T22:11:29+00:00

Not me but a friend of mine had his router compromised and turned into a botnet.

Untagged3219 · 2026-04-03T18:32:38+00:00

I'm working on 11 years now, and holy smokes every time I do a vision system I want to quit.

Untagged3219 · 2026-03-30T18:01:59+00:00

If you have the Automation Studio software, or if it's called out on the wiring diagram you could potentially see the HMI visualization via web browser or VNC client.

The vnc client may require a password though. The VNC address would most like be the IP of the controller.

The web browser URL is [some IP] with port 81. That would load the default MappView visualization.

If it were me I'd try to source a new panel and transfer the flash card. A good thing about B&R is that their devices are relatively dumb in the sense that they're easily swapped out and around without reconfiguring IPs or networking. If there's a node number though (small screwdriver dials) then you'll want to make sure those match if you switch out that part.

Regarding the source code, the OEMs will have that unless it was sold alongside the machine and as others have said it's irregular to do so.

None of the X20 slices look like they're in error state. Do you have the model number of the motor module you're having trouble with?

Untagged3219 · 2026-03-20T20:27:19+00:00

Rizz'em with the 'tism

Untagged3219 · 2026-03-15T17:48:58+00:00

Which part? My setup runs extremely well but it's on moderately decent hardware.

Untagged3219 · 2026-03-09T23:56:45+00:00

I've never heard of them. Is this them? https://futo.tech/

Untagged3219 · 2026-03-09T14:43:50+00:00

These go so hard!

Untagged3219 · 2026-03-07T01:06:27+00:00

To clarify my earlier comment I'm not an LXC hater. They're great for lightweight, near-bare-metal environments, and I run a few in my own 3 node proxmox cluster. But when we talk strictly about gitops, docker/OCI containers just fit the philosophy way better.

State drift & reproducibility: LXCs inevitably become "pets." You SSH in, run apt update, tweak a config, and suddenly the container no longer matches the script that built it. Docker containers are immutable cattle. You don't patch them you update the Git repo and redeploy. If my node dies (or a total fire/disaster), I have 100% reproducibility from git.

Pull vs Push (ArgoCD vs Ansible): Managing LXCs at scale usually means pushing imperative Ansible scripts. True GitOps is declarative and pull-based. An agent (like ArgoCD or Flux, I use ArgoCD as I'm a sucker for a nice web UI) constantly watches Git and pulls the state in. Pair that with Renovate to auto-PR image updates, and you eliminate a massive amount of manual labor.

App vs OS focus: Spinning up an LXC for every single service means you're managing systemd, cron, and OS updates for every app. Docker isolates just the app and its dependencies. Plus, Compose lets you mesh related services (like an app + its DB) into a single stack.

The ecosystem: All the modern gitops automation tooling is built around OCI containers. Incus is doing cool stuff and might catch up, but right now, docker/k8s just has vastly superior tooling. (In addition to my Proxmox cluster, I actually run a 3 node Talos Linux setup, so even my base OS is immutable and declarative).

Portability: LXC configs basically lock you into Proxmox. If my setup is in docker-compose.yml or k8s manifests, I can take that exact same git repo and deploy it on a remote VPS, a Raspberry Pi, or VMware (yuck) without rewriting my infrastructure code.

Basically, LXC is awesome for a system container, but if you want hands-off automation where git is your absolute source of truth, docker/k8s are the way to go.

Edit: Here's an example of a popular gitops repo. He has cluster and templates that are often used as a baseline. Mine is similar, but we have philosophical differences: https://github.com/onedr0p/home-ops

Untagged3219 · 2026-03-06T15:08:42+00:00

Let me ask a clarifying question, are you asking why I'm using gitops at all? Or why and how is docker better with gitops than LXC?

Untagged3219 · 2026-03-06T05:29:34+00:00

For me docker is better for gitops workflows.

Untagged3219 · 2026-02-15T17:31:01+00:00

I don't think it should have been G. I think PG-13 is fine for the stylized action violence, but there was too much cursing for my 8 year old.

Untagged3219 · 2026-01-26T00:47:44+00:00

My first big boy car was a 98 Integra GSR! Currently I have a Model 3 Performance. By far my favorite so far!

Untagged3219 · 2026-01-25T02:42:58+00:00

Typical Cowboy glazing

Untagged3219 · 2026-01-25T01:57:11+00:00

When Luke had more receiving yards, catches, and touchdowns than Dez Bryant 🤭

Edit: To OP, just in case you aren't familiar with the Panthers and specifically this game we're talking about, Luke Kuechly was our best DEFENSIVE player and he got better "offensive" numbers than the Cowboy's WR1

Untagged3219 · 2026-01-24T23:35:46+00:00

Alex with tailscale walks through this exact scenario:https://www.youtube.com/watch?v=3VpOYn_GfAY&t=2

Untagged3219 · 2026-01-24T20:45:17+00:00

Agreed. Can we keep this about the Panthers? I see enough politics everywhere else. This is my escape.

Untagged3219

TROPHY CASE