Hi Clement, On 2025-06-04 17:23, LONGEAC Clement wrote: > I have implemented podman as follows: > > rocm-podman-create debian:unstable.img > > autopkgtest -B silx -- podman+rocm debian:unstable.img
And this works, right? > I added in the sbuild config file : > > $autopkgtest_opts = ['--shell-fail', '--apt-upgrade', '--', > 'podman+rocm', 'rocm/debian:%r']; > > When I run autopkgtest for the ufo-filters package, where it is necessary to > fetch https://plmlab.math.cnrs.fr/tomogroup/ufo-testing.git > > Now when I run an sbuild without the podman+rocm implementation, the test > passes, no proxy problem. I don't quite follow. You say the test passes, so I guess you mean sbuild and autopkgtest with the regular 'podman' backend instead of 'podman+rocm'? > But when I run autopkgtest with podman+rocm , I get the following error: > > Cloning into 'ufo-testing'... > fatal: unable to access > 'https://plmlab.math.cnrs.fr/tomogroup/ufo-testing.git/': Failed to connect > to > plmlab.math.cnrs.fr port 443 after 135130 ms: Could not connect to server > autopkgtest [16:04:12] > > My question : How to integrate the http and https part to the chroot > used by podman ? > How do I set up the proxy for podman in > /etc/environment? Is this a problem with https and http, or only with https? You can start a container interactively to play around and see what works: # regular backend $ podman run --rm -it debian:unstable.img # backend which includes AMD GPUs # rocm-podman-run --rm -it debian:unstable.img Best, Christian
