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
Just a quick reminder that the next Podman Community Meeting is
happening next Tuesday November 3, 2020 at 11:00 a.m. EST (UTC-5). The
meeting is free to attend via BlueJeans video conferencing and is
scheduled for an hour.
Two quick notes:
o The US is turning the clocks back one hour this Sunday
November 1, so our UTC offset is shifting from -4 to -5.
o There's a little election going on in the USA on the meeting
date. If you're in the US and this time is the only time you can get
out and vote, please go vote. We'll be recording the meeting and you
can watch it after you vote.
The agenda is here: https://podman.io/community/meeting/agenda/ and
includes the BlueJeans link for the meeting and the HackMD link where
we'll take the meeting minutes.
Hope to see a bunch of you there!
The goal is to collect shortnames of container images at particular
registries. Would love to get lists of images specific to
distributions. Prepopulated with the images from Fedora, since they
were fairly easy to gather.
Since the Repo is brand new please open PRs to fix up the README.md or
any problems that you see.
Just a quick reminder that the next Podman Community Meeting is coming
up two weeks from today, Tuesday November 3, 2020 at 11:00 a.m. Eastern
time (UTC-05:00). A couple notes about that. A) The USA is "falling
back" on Sunday November 1 to Eastern Standard Time. So our UTC offset
will be -05:00 instead of -04:00. B) Secondarily, there happens to be a
little election going on in the USA that day. If you are US based and
you have not voted by that time and the only time you can vote is during
the meeting time, please go vote. We will be recording this meeting so
you can replay it afterwards.
We have a couple of topics lined up for the meeting already. Anders
Bjorklund will be talking about boot2podman/podman-archive (basically a
varlink post-mortem) and Brent Baude will be talking about Red Hat's
perspective on the direction of the future design for Podman. We also
have some time set aside for Questions and Answers, so start thinking
of some questions that you'd like answered!
If by chance you have a topic that you would like to discuss or present
upon, please let me know. We might be able to add it to this meeting,
and if not, then for a future one.
We will again be using BlueJeans to video conference
(https://bluejeans.com/796412039) and we will also use HackMD to take
notes (https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w). I will send out a
finalized agenda later next week. Like last time, no cost to attend.
Hope to see a bunch of you there!
I want to build this and from the Jitsi Manual Installation guide I have
marked up the attached diagram - can people see any issues with building
this container with Fedora and Podman? - has anyone tried it already? -
is anyone else interested in helping / co-operating?
PO Box 896
Cowra NSW 2794
I'm currently looking for advice on using Podman to implement what I think
is a fairly common application scheme, deploying a WordPress instance with
a MariaDB backend and Nginx as a reverse-proxy.
Ideally I'd like to recreate a DMZ approach where the reverse proxy doesn't
have access to the database or any other containers on the host. I have
almost accomplished this with Docker Compose by attaching a frontend
network to the reverse proxy and the application containers and a backend
network to the application and database containers. This is a complicated
approach and doesn't solve the issue of all application containers being
accessible from the reverse proxy container.
I have tried two different approaches to accomplish something similar with
Podman, but they both ended with essentially the same result.
Method one: Enclose all three containers in a single pod. These pods can
access each other via localhost:port. This approach is not ideal because
the reverse proxy container has access to both the application and database
Method two: Create a new network, cni-podman0, with the dnsname CNI plugin
and each container is created in its own pod. This approach is also not
ideal because any container on the cni-podman0 network can access any other
container on the same network using the pod's name (even if containers and
pods do not have published ports).
Any suggestions on where to go from here? Could SELinux or BPF be possible
solutions or am I missing an easier solution? I also thought about
assigning IP addresses to each pod and using the firewall CNI plugin to
lock down access by IP and port, but limited documentation on integrating
Firewalld and Podman has limited me from experimenting further.
I realize Kubernete's service and network policy features essentially
solves this problem, but I am looking for a simplified single host approach
I'm not sure why, but the original of this email was bounced by the
server. I'm sending it again with my answer.
-------- Forwarded Message --------
Subject: Newbie Question
Date: Sat, 10 Oct 2020 05:04:01 +0000
From: Jonathan Aquilina <jaquilina(a)eagleeyet.net>
To: podman-bounces(a)lists.podman.io <podman-bounces(a)lists.podman.io>
I have a quick question regarding podman, is it meant to be a
replacement for docker and or Kubernetes, or does it work hand in hand
Simple answer Yes.
Podman can work alongside of Docker or it can replace it. As noted on
the podman.io website:
Simply put: *alias docker=podman*.
We also work with Kubernetes with these commands:
But for a richer Kubernetes environment, you might want to look at CRI-O
https://cri-o.io/ and it's GitHub repo
(https://github.com/cri-o/cri-o). Others more involved than I with the
Kubernetes side of things will likely have more insight.
Welcome to the Podman community!
Just a quick thank you to the 34 attendees that joined us for the very
first Podman Community Meeting this past Tuesday October 6, 2020. As
mentioned previously, we're planning to hold these meetings on the first
Tuesday of the month at 11:00 a.m. Eastern time. The next meeting will
be on Tuesday November 3, 2020 at 11:00 a.m. Eastern again. As this
coincides with Election day in the US, we plan to record the meeting for
later consumption in case that time works best for you to get out and
vote. More details on the meeting will be sent with the agenda about a
week prior. We've a couple of discussion points already, please feel
free to send others to me.
Also I've just posted the meeting notes from the last meeting up on the
podman.io site at: https://podman.io/community/meeting/2020-10-06/. I
need to add a link on the "Join Our Community" to the new meeting page,
that's a WIP.
Thanks again to all of you who attended and looking forward to seeing
you on November 3!