podman system service and qemu
by Hendrik Haddorp
Hi,
using "podman run --arch ..." it's quite easy to start containers for a
different architecture with the support of qemu. "podman system service"
does however not seem to have the same support. I would like to use a
docker build from existing tooling for a different architecture. So this
would use the docker API that the podman system service provides. I
guess it should be possible to start a container using podman run --arch
an then start the podman system service in there. Is there a simpler way
as podman in podman has quite often some setup issues and the whole
handling would be more complicated?
thanks,
Hendrik
1 year, 7 months
Execute command on exit (?)
by Prafulla Giri
Hello there,
I have bind-mounted a local dir inside a container. Once the container is closed the directory permissions are
changed to a subuid and I have to run `podman unshare chown -R 0:0 /path/to/dir` manually if I want to do anything
with the bind-mounted directory. I was wondering if there is a method whereby a container (or a pod) could be configured
to do this automatically? I'd be glad to know about it (or any other ways to get around this minor issue).
Thank you.
1 year, 7 months
podman openmpi container
by ugiwgh＠qq.com
I have read article on https://podman.io/blogs/2019/09/26/podman-in-hpc.html.
And I have built openmpi image with fedroa.30 and centos.7.9.2009.
The hello_c runs successfully on fedroa.30 image.
But hello_c failed to run on centos.7.9.2009. It hang when runs on centos.7.9.2009 image.
I run it with -d, and it hang at "[rsyncdk2:2674797] [[58966,0],0] Releasing job data for [INVALID]".
The following is the whole message.
[rsync@rsyncdk2 ~] mpirun -d -v -host rsyncdk2:2 podman run --rm --env-host --userns=keep-id --network=host --pid=host --ipc=host 69fb54f4bb75 /home/hello_c
[rsyncdk2:2674797] procdir: /tmp/ompi.rsyncdk2.1000/pid.2674797/0/0
[rsyncdk2:2674797] jobdir: /tmp/ompi.rsyncdk2.1000/pid.2674797/0
[rsyncdk2:2674797] top: /tmp/ompi.rsyncdk2.1000/pid.2674797
[rsyncdk2:2674797] top: /tmp/ompi.rsyncdk2.1000
[rsyncdk2:2674797] tmp: /tmp
[rsyncdk2:2674797] sess_dir_cleanup: job session dir does not exist
[rsyncdk2:2674797] sess_dir_cleanup: top session dir not empty - leaving
[rsyncdk2:2674797] procdir: /tmp/ompi.rsyncdk2.1000/pid.2674797/0/0
[rsyncdk2:2674797] jobdir: /tmp/ompi.rsyncdk2.1000/pid.2674797/0
[rsyncdk2:2674797] top: /tmp/ompi.rsyncdk2.1000/pid.2674797
[rsyncdk2:2674797] top: /tmp/ompi.rsyncdk2.1000
[rsyncdk2:2674797] tmp: /tmp
[rsyncdk2:2674797] [[58966,0],0] Releasing job data for [INVALID]
1 year, 7 months
Podman contribution inquiry
by Calin Georgescu
Dear maintainers of the Podman repository,
We are a group of four computer science master students from the Delft University of Technology in the Netherlands following the course IN4315 Software Architecture (https://se.ewi.tudelft.nl/delftswa/). For this course we have chosen an open-source project to contribute to in the following eight weeks. Our group picked the Podman project, and we will therefore make a set of contributions for our project.
The project consists of two parts: firstly, we will write four essays discussing architecture choices that we will publish on https://desosa2022.netlify.app/. Secondly, we need to make between three and six code/documentation contributions to your repository to learn the workflow for contributing and to be able to dive deeper into the analysis. This is our first time contributing to open-source projects, and we are looking forward to assisting you with valuable contributions wherever it is most appropriate.
We would greatly appreciate it if it would be possible to open a channel of communication with you, where we could get some guidance and feedback on the contributions we produce. We are currently in the process of choosing the most appropriate issues to focus on throughout the duration of the course. We plan to contribute to increasingly more complex tasks as we become more familiar with the system, but it would be of great benefit to us if you could suggest some possible starting points, such as perhaps good first issues to focus on.
We have already gone through the process of selecting some issues that may be practical first choices, such as https://github.com/containers/podman/issues/13261 and https://github.com/containers/podman/issues/13266. If there are more appropriate contributions to focus on for our group, we would be happy to consider them!
Also, we checked the /doc directory in the repository and the published documentation on the podman website. It seems to us that they are mainly functioning as a guide for users. It would be nice if you could direct us to some technical, developer-centric documentation. Or if such a portal is not yet available, perhaps this could be one of our initial contributions?
Thank you for your time and consideration. If you have any questions or remarks, feel free to reach out to us through email or GitHub.
Kind regards,
Krzysztof Baran @kbaran
Rover van der Noort @rvandernoort
Xueyuan Chen @keonchennl
Calin Georgescu @gcalin
1 year, 7 months
Changing shell for RUNs in Containerfile without SHELL instruction
by Hans F
Hi folks,
Could you please tell me is there an easy way how to use something like SHELL instruction in Containerfile? OCI specs don't support SHELL so by default "podman build" requires --format docker but I would prefer to avoid it an use "pure" Podman / OCI.
I would like to use something like:
SHELL ["/bin/bash", "-c"]
So I can use Bashisms like for example:
RUN tee file <<< 'hello'
instead of:
RUN bash -c "tee file <<< 'hello'"
(I know I can echo hello | tee file, this is just a stupid example of Bashism.
I was thinking changing ENTRYPOINT at the beginning of Container file to
ENTRYPOINT ["/bin/bash", "-c"]
But that doesn't work...
Any suggestions are most welcomed ;-). (just please don't suggest not using Bashisms, I like them! ;-))
Thank you.
Hans
1 year, 7 months
Setting hostname in Kubernetes Pod Yaml
by Rudolf Vesely
Hi Everybody,
I’m not sure if this is a Kubernetes standard behavior or Podman bug/feature.
When I:
==================================================
tee test-this.yml <<< 'apiVersion: v1
kind: Pod
metadata:
name: mypod123
spec:
hostname: test456
containers:
- name: first
image: docker.io/library/debian:bookworm
command: ["/bin/sleep"]
args:
- "infinity"
- name: second
image: docker.io/library/debian:bullseye
command: ["/bin/sleep"]
args:
- "infinity"
- name: third
image: docker.io/library/ubuntu:focal
command: ["/bin/sleep"]
args:
- "infinity"'
podman play kube test-this.yml
==================================================
and then:
==================================================
podman exec mypod123-first cat /etc/hostname
test456
podman exec mypod123-first hostname
mypod123
==================================================
And when I "podman exec -it mypod123-first bash" I can see "root@mypod123" in the prompt.
In other words "spec.hostname" does change "/etc/hostname" but does not apply it like reboot on host would do.
Can anyone please tell me, is it a bug or feature?
Thank you.
Kind regards,
Rudolf Vesely
1 year, 7 months
Upgrade Recommendations from 1.4.2 to 3.3.1
by Christopher.Miller＠gd-ms.com
Hello, currently running Podman 1.4.2 on RHEL 8.1 and want to upgrade 3.3.1 so we can take advantage of the newer features (like networking).
I am running containers currently in the 1.4.2 environment. Is there anything to think of or do before doing an upgrade, or a best practice?
Thanks
Chris Miller
Altron INC.
703-814-7647
Christopher.miller(a)altroninc.com
Christopher.Miller(a)gd-ms.com<mailto:Christopher.Miller@gd-ms.com>
1 year, 7 months
