I run poudriere in a jail on FreeBSD – it really is becoming the thing-to-do with all the cool kids. Everyone’s doing it. It is nifty. I will provide only the jail configuration, and not any file system configuration. That is left for you. I think these links might be most helpful: Using poudriere to […]
Configuration for running poudriere in a jail on FreeBSD 14 Read More »
I see see these log messages on a regular basis. There is no distinct pattern. Some nights there might be 1, others 2. Today there were three: r730-01 is my main server in the basement. It runs a jail named pkg01, which does my nightly poudriere builds. Those jobs are launched from this crontab: That
kernel: pid 4900 (conftest), jid 968, uid 65534: exited on signal 11 (core dumped) Read More »
NOTE: If you’re looking for a jail configuration for poudriere, please refer to Configuration for running poudriere in a jail on FreeBSD 14. I recently moved the pkg01 jail from one host to another. I’m having trouble getting it to build packages. [pkg01 dan ~] % sudo poudriere testport -j 131amd64 -p dvl -z primary
Moving the poudriere jail from slocum to r730-01 Read More »
In this post, I will talk about how I modified my pkg configuration so I don’t have to modify it after upgrading a host/jail from one version of FreeBSD to another. You might say that you don’t have to do that. Perhaps you have a different configuration and aren’t doing what I’m doing. HEADS UP:
Making my pkg.conf configuration version independent Read More »
This started off as a Twitter thread earlier this morning. databases/mysql57-client has an optional dependency on security/cyrus-sasl2 which defaults to on. Let’s try turning that off and see if it also removes openldap-client from the dependency list. Why? I install net-mgmt/nagios-plugins in just above every jail and host. Even hosts which don’t use MySQL. I
Turning off SASLCLIENT for databases/mysql57-client Read More »
Last last night, after renaming some buildlists, which were actually setnames, for poudriere, I realized that files in /usr/local/etc/poudriere.d also needed to be renamed. In this post: poudriere 3.3.7 nginx 1.20.1_2,2 Both running on FreeBSD 13.0-RELEASE-p4 These are my renamed files: [dan@pkg01:/usr/local/etc/poudriere.d]: $ ls *primary* primary-make.conf primary-poudriere.conf primaryi386-make.conf primaryi386-poudriere.conf The output of svn status illustrates
poudriere: when renaming sets, also rename *-make.conf files etc Read More »
I like readability. I like it in variable names. I prefer something descriptive and easy to ready. In in this post: FreeBSD 13.0-RELEASE-p4 poudriere 3.3.7 I recently started getting messages like this from my daily poudiere build: I could just rename the sets, everything would be rebuilt, but then clients would be stuck pointing at
This post was originally a few tweets. It’s not really about upgrading vulnerabilities in poudriere jails either. Read this as if each paragraph was a tweet. When a FreeBSD security alert comes out, or a package is marked as vulnerable, I try to get that fixed as soon as I can. Even if not using
Fixing vulns in poudriere jails Read More »
This post is all about moving poudriere from the host into a jail, but you could probably use it for creating a new jail and running poudriere in it. NOTE: If you’re looking for a jail configuration for poudriere, please refer to Configuration for running poudriere in a jail on FreeBSD 14 – it contains
Moving poudriere from the host into a jail Read More »
zi0r suggested I use hooks to accomplish my patches-outside-distfiles question. In this post: FreeBSD 12.0 poudriere 3.3.2 I started reading the documentation and played with the supplied sample files in /usr/local/etc/poudriere.d/hooks. For background, see FreeBSD custom port patches when using poudriere. Eventually I came up with this solution: mkdir during the start phase mount during