I can run the discourse image with docker, export the container and
import it as an image into podman.
The script that manages docker discourse containers is:
and is attached. It would be good if it were possible to just replace
all the occurrences of "docker" with "podman", fix version numbers etc
and be able to use the script - but can any gurus see dockerisms in the
script that will cause podman gotchas for this idea?
PO Box 896
Cowra NSW 2794
I am in an attempt to "force" all users that execute podman to run as a regular user inside of the container. Is there a configuration file or a wrapper script available to accomplish this? I understand users can pass the -u option at the command line and specify an user ID/group ID, but I want to see if there is a way to do this globally from the operating system without passing command line options. I am on RHEL 7 baseline.
This is more about fixing the perception of users running in a privileged mode with a technical control for our information security team.
Update on Podman V2
A few weeks ago, we made an announcement about the development of
Podman V2. In the announcement, we mentioned that the state of
upstream code would be jumbled for a while and that we would be
temporarily disabling many of our CI/CD tests. The upstream
development team has been hard at work, and we are starting to see that
work pay off.
Today, we are very excited to announce:
The local Podman v2 client is complete. It is passing all of its
rootfull and rootless system and integration tests.
The CI/CID tests have been reenabled upstream and are run with each
pull request submission. We are now hard at work finishing up some of
the core podman-remote functions. Once those functions are complete,
we can then begin to run our podman-remote system and integration tests
to catch any regressions.
We have re-enabled the autobuilds for Podman v2 in Fedora rawhide. As
mentioned earlier, the Podman remote client is not complete, so that
binary is temporarily being removed from the RPM. It will be re-added
when the remote client is complete. As a corollary, the Windows and
OS/X clients are also not being compiled or tested. This will occur
once the remote client for Linux is complete.
We encourage you to pull the latest upstream Podman code and exercise
it with your use cases to help us protect against regressions from
Podman v1. We hope to make a full Podman v2.0 release in several
weeks, once we are confident it is stable. We look forward to hearing
what you think, and please do not hesitate to raise issues and comments
on this in our [GitHub repository](
https://github.com/containers/libpod/issues), our Freenode IRC channel
`#podman`, or to the Podman mailing list.
We’re very excited to bring Podman v2.0 to you as it offers a lot more
flexibility through it’s new REST API interface and adds several
enhancements to the existing commands. If your project builds on top
of Podman, we would especially love to have you test this new version
out so we can ensure complete compatibility with Podman v1.0 and
address any issues found ASAP.
Note: This announcement was first released to the Podman mailing
list. If you are not yet a member of that community, please join us by
sending an email to [podman-join(a)lists.podman.io](mailto:
podman-join(a)lists.podman.io?subject=subscribe) with the word
“subscribe” as the title.
Regarding the email thread:
"We are working on creating a FAQ for Podman"
I'm curious about the question:
What are the main differences between Podman and Singularity?
I think in the academic world Singularity has become quite popular.
The PhD students in my work place build the SIF (Singularity Image
Format) file on their local computer and then copy it to the cluster
with the scp command and run it there. (In some research HPC compute
clusters they have installed Singularity)
(Not so much of an answer but I tried to describe the situation where
I get the question).
Here are some of the questions we have now.
Q: What is Podman?
Q: How is Docker different from Podman?
Q: Can Podman run all container images stored at container registries
like the Docker hub?
Q: What does “rootless” mean?
Q: What does the name “Podman” mean?
Q: What is a POD?
Q: What is the difference between Buildah and Podman?
Q: Can I use Podman to run Kubernetes?
Q: Can Podman run containers on Windows?
Q: My rootless container doesn’t have an IP address; is this a bug?
Q: Does Podman require containerd or CRI-O?
Q: Where’s the documentation for Podman?
Q: Does Podman work with Docker?
Q: Can Docker and Podman be installed at the same time on a system.
But we would love to hear from you on what questions you would like to
have answered. Including the Answer would also be appreciated.
Please fire away.
Hey pod-folk –
In the Kata Containers community, for 2.0 Kata we are looking to *just* support integration through a gRPC server/client interface, utilizing the ‘v2-shim’ API. This is how we integrate with CRIO/containerd, and we are now looking at do similar for both moby and Podman.
I wanted to get feedback from Podman community on whether integrating through v2shim server/client between podman/kata is:
1. Technically feasible
2. A design pattern ya’ll are amenable to.
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Ampere Computing or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. Any review, copying, or distribution of this email (or any attachments thereto) is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.