Recently I tried to run docker-compose with some example compose files and they all worked very nice. Great job! And thank you!
The only thing that I cannot run is https://github.com/mistio/mist-ce
After modifying image paths from "abc" to "docker.io/library/abc <http://docker.io/library/abc>" I can run docker-compose.yml with Podman 3.4.4 without errors and all containers that would normally run with Docker do run after docker-compose up -d. So it's difficult to say what went wrong...
If you look at the compose: https://github.com/mistio/mist-ce/releases/download/v4.6.2/docker-compose...
It's definitely complicated so it doesn't surprise me that something broke.
Has anyone tried please?
Various "howtos" on the net rarely mention SSL and I get -
after such repo deployment - 'pull' complaining about HTTP,
until I added certs.
Question - perhaps it's not allowed by recent 'podman'
versions to have insecure repo?
registries = ["mine.private:5000",
"registry.centos.org", "quay.io", "docker.io"]
registries = ['mine.private:5000']
many thanks, L.
I am running a pod via play kube. My container exits, but the companion infra container keeps running forever, meaning that the whole pod keeps running forever
Is there a way to make infra container exit once pod's containers exit?
I am running on OSX
Having a local repo - what would need to done to replicate
it over to another host?
Only mapped volume of the container '/var/lib/registry'
being synced over does not seem to be enough, so I presume
it would have to whole container image but, how would that work?
And very next thing I'd wonder is - is separate storage path
per image allowed or even possible?
Or maybe there is another ready-made solution I'm unaware of?
many thanks, L.
First of all, thanks for Podman.
I'm working in a service which will have a pod with 3 containers.
This service (syslog relay) will be served in the network via an
I've BGP peering working with bird. Each pair peer and interface
have a dedicated routing table. Pod is also working and configured in
rootless mode, configured with network configures as
Quick diagram to explain my problem.
| | | |
| peer 1 | | peer 2 |
| | | |
| int 1 int 2 int 3 |
| dummy |
| ip anycast |
| | Host
At this time, the pod is running and if I send syslog to IP in
interface 3 (int 3, in routing table main), the messages arrive at
container (tcp or udp). But if the messages are sent to Anycast IP
(configured in interface dummy) it does not arrive at containers.
I've already saw to possibilities to solve the problem:
- Rudolf Vesely (DIY networking for rootless containers/pods)
- Using Calico CNI with podman
But, before deep dive in more complex solutions, I'm requesting
your help to see if I missing some more basic in my configuration. I'm
trying to keep the configuration as simple as possible because in future
this solutions will be supported by a team which as less knowledge in
this than me.
Thanks in advance.