re:fi.64 :bisexual:

Website: https://refi64.com/
Vaccinated?: x5
Pronouns: he/they

Last Notes

2026-05-06 13:14:00 GMT

- reply

okay I just saw your other post where you mention it's rootful podman, a thing I momentarily forgot exists 😭 but in that case, some of the hints in https://github.com/containers/podman/issues/10729 might be useful? in particular iirc the macvlan driver in docker land has the side effect of not allowing host system access. less sure what they meant wrt the parent bridge suggestion.

2026-05-06 13:04:58 GMT

- reply

I am Not A Networking Person, but I suspect that at least some bits of this can be fixed by passing custom options directly to the networking backend, probably pasta: https://passt.top/builds/latest/web/passt.1.html in particular, the address and/or output option might be useful to get the containers into a different firewall zone, and the port options there *might* let you get around the internal network restrictions altogether (but I'm extremely unsure about that)

2026-03-09 03:52:11 GMT

- reply

this is a bit besides the point, but for the sake of completeness, Gemini 3 Pro in ai studio does manage to find it (if I understood the issue correctly, at least). that being said, it only found it for stdout, not stderr, and ofc amidst a bunch of nitpicks (none related to allocation failures though). nothing else I tried got this far.
https://files.refi64.social/media_attachments/files/116/197/184/684/583/507/original/b3c48403086a2835.png

2025-02-03 19:29:56 GMT

- reply

I am most definitely *not* an expert here, but I *think* you could this via gstreamer, since it would let you demux it but keep the same h264 frames, and then mp4mux has options to let you set the timescale on the new container.
(But it's not entirely clear to me that this is what you want, I'm not sure what parts of this are in the h264 data vs the container... Also yeah this isn't ffmpeg, but at least it avoids the mkv round-trip?)