rhatdan

8 ms·

31.
by rhatdan 4y ago
Podman will run as root or rootless mode, depending on how you want to run your container. Each user on your system can run containers in their home dir, or if you need extra privileges you can run the containers as root. We have found ver
32.
by rhatdan 4y ago
Podman believes the future is Kubernetes. It supports kubernetes.YAML just like regular Kubernetes and OpenShift. But runs the Pods and containers locally. Checkout podman kube play as an alternative to docker-compose, even has --build an
33.
by rhatdan 4y ago
You should be able to runc docker-compose (v2) against a podman socket activated service.
34.
by rhatdan 4y ago
The goal with Podman was to allow you to easily learn either and move back and forth. Similar to moving between web browsers or file systems.
35.
by rhatdan 4y ago
fuse-overlay has some support for this, but it is fairly experimental. Basically it allows mapping of all files to a single UID, and then stores container owners/permission in XAttrs. When fuse-overlayfs exposes the image to the cont
36.
by rhatdan 4y ago
Podman is supported as a gitlab-runner now, as I understand it. https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29108
37.
by rhatdan 5y ago
Podman works with docker-compose in rootless mode, no need to set up the security questionable DOCKER Group.
38.
by rhatdan 5y ago
Yes Podman supports the Docker API and supports docker-compose directly a opposed to podman-compose which uses podman commands directly by reading the compose format and generating podman commands. docker-compose2 has a bug with Podman righ
39.
by rhatdan 5y ago
This is no longer true. As of kernel 5.13 podman can use rootless native overlay.
40.
by rhatdan 5y ago
This is what the the podman-machine github says under the DEPRECATED section: ` DEPRECATED: Podman v3.3 now has a podman machine included, different from podman-machine This is a new feature based on QEMU and CoreOS, unlike the old one (des
41.
by rhatdan 5y ago
podman-machine was a project disconnected from Podman. The podman project recently added a new command to podman `machine`. The `podman machine` command downloads and runs VMs with the podman service enabled within them. It also configures
42.
by rhatdan 5y ago
Note: Every mainstream OS since RHEL8 has defaulted to User Namespace being turned on. Debian, Fedora, Ubuntu, RHEL, Centos ... all have this defaulted on. While overall the statements are true. There has not been many recent vulnerabilitie
43.
by rhatdan 5y ago
You can volume mount in the host container storage into the container using additional stores. In this article, note sections on /var/lib/shared https://developers.redhat.com/blog/2019/08/14&#x2
44.
by rhatdan 5y ago
This is no longer true. As of kernel 3.11 native overlay can be used by rootless users.
45.
by rhatdan 5y ago
No true. Podman runs natively on a MAC, using a Linux VM for containers, just like Docker. `podman machine init` pulls down a VM, after which you can start running, developing, and building the same images that Docker and Kubernetes use. J
46.
by rhatdan 6y ago
containerd is a daemon, which actually came out after CRI-O. But anyways the hole idea is Podman and Buildah was to get away from using root running daemons to launch containers. The important thing about containers is that we launch we a
47.
by rhatdan 6y ago
Hopefully most of you who have had issues with Podman have opened bug reports or issues. We are working to fix incompatibility bugs and getting out new releases all the time. As far as docker-compose support, in Podman 2.0 we have added API
48.
by rhatdan 8y ago
Look for a backported shadow-utils in RHEL7.7, which is scheduled for the summer. RHEL8.Beta currently supports rootless podman 1.0.
49.
by rhatdan 8y ago
The difference is that buildah's only job in the world is to build OCI Images. Podman is more about running containers so It's containers are a lot more generalized. Buildah containers and buildah run are far different in concep
50.
by rhatdan 8y ago
Right there are many reasons to run podman as "real" root as well. Using containers within systemd unit files, is one use case. Setting up a docker daemon to run a single container at boot is way overkill. If you just use podma
51.
by rhatdan 8y ago
Well rootless podman works before 1.0, but we have had many issues to work out. Overall it works very well.