12-stable, poudriere in jail
Stefan Bethke
stb at lassitu.de
Fri Dec 14 15:09:44 UTC 2018
No matter what I tried, the python and ruby builds still are failing.
I’ve since changed the setup to a VIMAGE vnet jail, and that appears to be working properly.
If there is a way to make the „classic“ inherited IPs setup work, I’d love to learn how.
Stefan
> Am 10.12.2018 um 00:20 schrieb Stefan Bethke <stb at lassitu.de>:
>
> I’ve made some progress fiddling with common.sh. If I hard-reset $localipargs to an empty string, I can run the build successfully. ATM for me, $localipargs is set to „ip4.addr=127.0.0.1 ip6.addr=::1“, which breaks the jail(8) invocation.
>
> I’ve opened an issue on GH: https://github.com/freebsd/poudriere/issues/657
>
>> Am 09.12.2018 um 21:17 schrieb Stefan Bethke <stb at lassitu.de>:
>>
>> Since upgrading my machine to 12-stable a couple of days ago, my poudriere jail is having trouble building python and ruby errors like:
>> checking getaddrinfo bug... yes
>> Fatal: You must get working getaddrinfo() function.
>> or you can specify "--disable-ipv6".
>> ===> Script "configure" failed unexpectedly.
>>
>>
>> compiling getaddrinfo.c
>> In file included from getaddrinfo.c:86:
>> ./addrinfo.h:165:12: error: conflicting types for 'getnameinfo'
>> extern int getnameinfo __P((
>> ^
>> /usr/include/netdb.h:251:6: note: previous declaration is here
>> int getnameinfo(const struct sockaddr *, socklen_t, char *,
>> ^
>> getaddrinfo.c:408:7: warning: add explicit braces to avoid dangling else [-Wdangling-else]
>> } else if (strcmp(sp->s_proto, "tcp") == 0) {
>>
>>
>> My jail has a private IP assigned to an Ethernet interface, and a loopback address. In 11-stable, I shared 127.0.0.1 with the host. Since upgrading to 12-stable, I get
>> jail: IPv4 addresses clash
>>
>> If change the loopback IPs on the jail to .2/:2, I then get:
>> [00:00:00] Warning: No loopback address defined, consider setting LOIP6/LOIP4 or assigning a loopback address to the jail.
>>
>> but I get the above build errors. Setting LOIP4/LOIP6 to .2/:2, I’m back at the IPv4 addresses clash error. Setting LOIP4/LOIP6 to 3./:3, I get the warning again, and the build errors.
>>
>> I can build python on the host just fine.
>>
>> I’m getting the build problems with both a 11.2-RELEASE and a 12.0-RC3 based reference jail.
>>
>>
>> The relevant lines from jail.conf:
>> pkg {
>> path = "/jail/pkg.xxx.xxx";
>> host.hostname = „pkg.xxx.xx";
>> ip4.addr += "bridge1|44.128.xx.xx";
>> ip4.addr += "lo0|127.0.0.1";
>> ip6.addr += "lo0|::1";
>> children.max = 40;
>> exec.poststart += "zfs jail $name data/jail/${host.hostname}/poudriere";
>> exec.poststart += "jexec $name zfs mount -a";
>> #exec.prestop += "zfs unjail $name data/jail/${host.hostname}/poudriere";
>> allow.mount;
>> allow.mount.devfs;
>> allow.mount.linprocfs;
>> allow.mount.nullfs;
>> allow.mount.procfs;
>> allow.mount.tmpfs;
>> allow.mount.zfs;
>> allow.socket_af;
>> allow.chflags;
>> enforce_statfs=1;
>> #ip6=inherit;
>> ip4=inherit;
>> }
>>
>>
>> --
>> Stefan Bethke <stb at lassitu.de> Fon +49 151 14070811
>>
>> _______________________________________________
>> freebsd-ports at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>
> --
> Stefan Bethke <stb at lassitu.de> Fon +49 151 14070811
>
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
--
Stefan Bethke <stb at lassitu.de> Fon +49 151 14070811
More information about the freebsd-ports
mailing list