[DRBD-user] Building drbd-utils in a docker container

[Roland Kammerer]

On Fri, Mar 30, 2018 at 10:52:15AM +0200, Roland Kammerer wrote:
> On Wed, Mar 28, 2018 at 08:10:46PM -0700, Chuck Wolber wrote:
> > Hi,
> > 
> > This question seems to apply to all versions of drbd-utils from the current
> > version on back to 8.9.6. Beyond that, I did not have time to look.
> > 
> > I am building drbd-utils in a docker container for the purposes of
> > packaging it for installation in another system. The docker container does
> > not have udevadm or udevinfo installed in it, so the resulting drbd-utils
> > package contains a udev ruleset that is disabled.
> > 
> > Is there a "clean" way to pass an argument to the configure script to
> > override this behavior and ensure the udev ruleset is not disabled at build
> > time?
> 
> There is already a "--with-udev", which is, IIRC, on by default. This
> then queries pkg-config for the udev directory. That should be enough,
> isn't it?

Oh, it isn't, it then further down looks for udevadm/udevinfo, and adds
the suffix ".disabled" if not found.

So I suggest to get your docker image in a state where it matches the
build magic.

Regards, rck