#892612 ITP: conbuilder -- container-based package builder for

Package:
wnpp
Source:
wnpp
Submitter:
Federico Ceratto
Date:
2025-11-29 16:29:45 UTC
Severity:
wishlist
#892612#5
Date:
2018-03-11 11:31:43 UTC
From:
To:
* Package name    : conbuilder
  Version         : 0.0.1
  Upstream Author : Federico Ceratto <federico@debian.org>
* URL             : https://salsa.debian.org/federico/conbuilder
* License         : GPLv3
  Programming Lang: Python
  Description     : container-basade package builder for Debian packages

Build Debian packages using OverlayFS and systemd namespace containers.

conbuilder creates a base filesystem using debootstrap, then
overlays it with a filesystem to install the required dependencies
and finally runs the build on another overlay.

Layers are created, reused and purged automatically to achieve
fast package builds while minimizing disk usage.

It takes less than 2 seconds to start a new build on an already existing
overlay.

conbuilder also allows to selectively disable networking,
capabilities and filter system calls using seccomp.

The packaging will be hosted at [1] as a native package.

[1] https://salsa.debian.org/federico/conbuilder
#892612#10
Date:
2018-03-11 11:35:55 UTC
From:
To:
HALP! how do I unsubscribe.

~Seriously confused.
#892612#15
Date:
2018-03-11 11:45:05 UTC
From:
To:
I don't know what container-basade is. Is it a typo??
 s/basade/based/

Description : container-based package builder for Debian packages


Groeten
Geert Stappers
#892612#20
Date:
2018-03-11 12:01:24 UTC
From:
To:
'Container-based' ?

Wookey
#892612#25
Date:
2018-03-11 12:01:24 UTC
From:
To:
'Container-based' ?

Wookey
#892612#32
Date:
2018-08-01 14:28:54 UTC
From:
To:
Am Sonntag, den 11.03.2018, 11:31 +0000 schrieb Federico Ceratto:

What's the difference to sbuild which is configured to use overlays?
#892612#37
Date:
2018-08-01 15:38:42 UTC
From:
To:
Hi,

Quoting Benjamin Drung (2018-08-01 16:28:54)

There certainly are a few things like disabling network access during build or
seccomp filters which schroot in Debian cannot yet do (see also #802849).

But before re-implementing all the package building logic that already exists
in pbuilder and sbuild, could we maybe evaluate whether it is feasible to
extend the existing tools with a new backend?

Especially when added as an autopkgtest-virt server, such work would benefit a
much bigger crowd than yet another [1,2] package building software.

I would certainly appreciate a bug against sbuild that adds functionality that
sbuild does not yet have.

Thanks!

cheers, josch

[1] https://lists.debian.org/4340a82e-15fc-1518-122a-c49273da1e5a@metux.net
[2] https://lists.debian.org/87lhiduele.fsf@desiato.home.uhoreg.ca