[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/7] configure: expose the direct container command
|
From: |
Daniel P . Berrangé |
|
Subject: |
Re: [PATCH 1/7] configure: expose the direct container command |
|
Date: |
Mon, 27 Feb 2023 11:18:41 +0000 |
|
User-agent: |
Mutt/2.2.9 (2022-11-12) |
On Fri, Feb 24, 2023 at 06:08:51PM +0000, Alex Bennée wrote:
> In the process of migrating away from using docker.py to build our
> containers we need to expose the command to the build environment. The
> script is still a useful way to probe which command works though.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> configure | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
- [PATCH 0/7] testing/next: docker.py removal and kaniko updates, Alex Bennée, 2023/02/24
- [PATCH 1/7] configure: expose the direct container command, Alex Bennée, 2023/02/24
- [PATCH 2/7] tests/dockerfiles: unify debian-toolchain references, Alex Bennée, 2023/02/24
- [PATCH 7/7] tests/gitlab: use kaniko to build images, Alex Bennée, 2023/02/24
- [PATCH 6/7] tests/docker: use direct RUNC call to run test jobs, Alex Bennée, 2023/02/24
- [PATCH 3/7] tests/lcitool: append user setting stanza to dockerfiles, Alex Bennée, 2023/02/24