Remix.run Logo
marginalia_nu 7 hours ago

This is extremely tangential, but I was working on setting up some manual network namespaces recently, basically manually reproducing what docker does to fix some of its faulty assumptions regarding containers having multiple IPs and a single name causing all sort of jank, and had to freshen up on a lot of Linux virtual networking concepts (namespaces, veths, bridge networks, macvlans and various other interfaces), made a ton of fairly informal notes to make myself sufficiently familiar with the thing to set it up.

Would anyone be interested if I polished it up and maybe added a refresher on the relevant layer 2 networking needed to reason about it? It's a fair bit of work and it's a niche topic, so I'm trying to poll a bit to see if the juice is worth the squeeze.

HumanOstrich 5 hours ago | parent | next [-]

I was actually going down rabbitholes today trying to figure out how to do a sane Docker setup where all the containers couldn't connect to each other. Your notes would be valuable at most any level of polish.

esseph an hour ago | parent [-]

If you create each container in its own network namespace, they won't be able to.

HumanOstrich 16 minutes ago | parent [-]

It's a little more complex than that for any non-trivial layout where some containers do need to talk to other containers, but most don't.

msbhvn 6 hours ago | parent | prev | next [-]

Please do it, I'm very biased but I think there would be lots of interest in seeing all that explained in one place in a coherant fashion (you will likely sharpen your own understanding in the process and have the perfect resource for when you next need to revisit these topics).

ambicapter 4 hours ago | parent | prev | next [-]

I would absolutely be interested.

MrResearcher 5 hours ago | parent | prev | next [-]

Don't forget to post the link here!

manuelangel99 6 hours ago | parent | prev | next [-]

I would def. be interestred!

globalnode 3 hours ago | parent | prev [-]

i await your write up!