SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux
<darfo>
i only use iptables, no nftables. It doesn't seem to be due to missing kernel support but because it is specifically directing container-to-host traffic to an iptables DROP rule. docker 27.5.1 does not do that, just the newer 28.0.1.
<darfo>
I was mistaken earlier about port publishing. Container doesn't publish any ports for host use, only creates outbound connections and uses host for DNS, etc.
<darfo>
I've been reviewing the changelogs for docker 28.0.0 and 28.0.1 but I haven't found any information about new kernel support required in 28.x that was not required in 27.5.1.
<jaeger>
Does the check-config script from docker tell you anything useful?
lavaball has quit [Remote host closed the connection]
<darfo>
no, it has the same output for 27.5.1 and 28.0.1. it may not have been updated yet though.
<darfo>
but that was a great idea to check it
<darfo>
the DOCKER-ISOLATION-STAGE-1 chain is different with 28.0.1. It passes passes the packets to DOCKER-ISOLATION-STAGE-2 where it used to return. And DOCKER-ISOLATION-STAGE-2 is all -j DROP rules and drops the packet because it is supposed to go out to the host bridge interface.
<darfo>
28.0.0 release three weeks ago. 28.0.1 released two weeks ago to fix 28.0.0. 28.0.0 had a lot of changes so I imagine it is not going to stabilize for all use-cases until a another release or three :)
<farkuhar>
ppetrov^^: not to build the library; texinfo is only needed to build the documentation. Makefile targets: html dvi info pdf ps
<ppetrov^^>
well, building libmpfr broke
<ppetrov^^>
i had to install texinfo
<jue>
strange, works for me
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Here on a clean container it worked and on the rpi3 it requires texinfo too (I’m still trying to figure out what’s happening there)
<farkuhar>
ppetrov^^: Can you try inserting `autoreconf -ivf` before ./configure, and see if the build still fails with no texinfo?
<ppetrov^^>
i really need to have some beers right now
<ppetrov^^>
maybe later
<cruxbridge>
<tim> autoreconf does not help for me
<farkuhar>
opt/poppler 25.03 is eagerly linking to something not listed among the hard dependencies, resulting in a footprint mismatch (/usr/include/poppler/JPXStream.h replaced by /usr/include/poppler/JPEG2000Stream.h). Ignoring footprint is probably easier in this case, rather than cluttering the ports tree with another maintainer_clean_footprint.
<jue>
hmm, there is no JPXStream.h in the footprint of poppler?
<farkuhar>
Three previous poppler commits mentioned the JPXStream header: c44b8b29bda8c1b1a6c75768ae53514d4d6fce66 (2023-09-09), 0281dc843974e128588131398be02ab80284c798 (2024-02-04) and 136873f445299ceba55cefa2092bcec4ec74ff7c (2024-05-02). So it seems to find its way back into the footprint somehow. Interestingly, the file only appears in the 3.8 branch; poppler in the 3.7 branch doesn't have JPXStream.h.
lavaball has quit [Remote host closed the connection]
<cruxbot>
[core/3.7]: libmpfr: added sed to fix build