My gitea runner is using podman, and I want to use podman inside (to build and test my containers) as well. To this end, I am building the image used by the runner as:
FROM quay.io/podman/stable
RUN dnf install -y git nodejs && \
dnf clean all && \
rm -rf /var/cache/yum
ADD --chmod=755 https://github.com/docker/compose/releases/download/v2.27.1/docker-compose-linux-x86_64 /bin/docker-compose
USER podman
WORKDIR /home/podman
the podman commands run as expected, but for the docker-compose (which is pointing to podman socket, I have the same setup running locally for other containers), I am getting this error:
error during connect: Get "http://unix:2375/run/podman/podman.sock/v1.45/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%app%22%3Atrue%7D%7D": dial tcp: lookup unix on 10.89.0.1:53: no such host
Steps to reproduce the issue
Steps to reproduce the issue
run the docker-compose command while inside the podman container run by Gitea
Describe the results you received
error during connect: Get "http://unix:2375/run/podman/podman.sock/v1.45/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%app%22%3Atrue%7D%7D": dial tcp: lookup unix on 10.89.0.1:53: no such host
Describe the results you expected
The containers start as expected and my tests get run.
Issue Description
My gitea runner is using podman, and I want to use podman inside (to build and test my containers) as well. To this end, I am building the image used by the runner as:
Then, I am running a task on the runner as:
the podman commands run as expected, but for the docker-compose (which is pointing to podman socket, I have the same setup running locally for other containers), I am getting this error:
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Describe the results you expected
The containers start as expected and my tests get run.
podman info output
Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
No response
Additional information
No response