debian-forge-composer/distribution
Tom Gundersen c3185466ae containers: simplify Dockerfile and container build
This changes the following:
 - Only produce one container. There is no particular benefit to
   supporting several different base containers, so unify on ubi
   as that is what we need ourselves.
 - Build directly from git. Now that the RPM we include in our
   container does not have any dependencies and only contains a
   couple of executables, the indirection via RPM has less value.
   Eventually the value will be reduced even further as we merge
   the entrypoint into the main binary and move dnf-json into the
   worker, leaving us with only a go binary. The only potential
   benefit might be that the build environment of RPMs is more
   clearly defined, but there is no real reason to believe that
   our mockbuild is any better than using the UBI golang build
   container.

This simplifies the container builds, and brings us more in line
with what is done in image-builder, and what is needed to deploy
to openshift.
2020-12-22 15:27:39 +01:00
..
Dockerfile-ubi containers: simplify Dockerfile and container build 2020-12-22 15:27:39 +01:00
osbuild-composer-api.socket distribution: deprecate osbuild-composer-koji.socket 2020-10-16 09:37:04 +02:00
osbuild-composer.conf distribution: set permissions on api sockets 2020-05-20 01:55:26 +02:00
osbuild-composer.service composer: do not require the weldr socket 2020-11-17 17:01:18 +00:00
osbuild-composer.socket composer: split out the local worker socket 2020-11-17 17:01:18 +00:00
osbuild-local-worker.socket composer: split out the local worker socket 2020-11-17 17:01:18 +00:00
osbuild-remote-worker.socket sockets: clarify their descriptions 2020-11-17 17:01:18 +00:00
osbuild-remote-worker@.service Add Install section to remote worker unit file 2020-08-24 12:56:45 -05:00
osbuild-worker@.service composer: split out the local worker socket 2020-11-17 17:01:18 +00:00