-
|
Hi, I have a system deployed with docker (via docker-compose) in production grade. I've migrated this system to podman. I use podman 5.4.x and podman-compose 1.2.0. All of my containers have restart policy "always" in the compose file. One of my containers bind to podman.socket (linking docker.sock to podman.socket) hence using podman.socket service. Because it orchestrates other containers for some use-cases. The system is working as similar to my docker deployment. It works really fine. In your NEWS documentation for podman 5.4.1, you point out that podman-restart.service and podman.socket service is no longer activated by default. Since I use two of your services: podman-restart and podman.socket, I wonder the future of these services. In my situation, restart is sufficient and I do not need a systemd orchestration.
Please comment on possible drawbacks if you think that I should be aware of. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Are you talking about the debian changes? That is not us but the debian packager. Anyhow, we have no plans to remove these units. You just have to run systemctl enable on them on your own. There are a few problems with having them enabled by default that should be mentioned if you follow the debian bug reports but as long as you enable them intentionally it is fine. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @Luap99 for your response. Exactly yes, I mean debian changes. I thought like debian community has some insights from your side and you are the responsible for such statements in NEWS documentation. |
Beta Was this translation helpful? Give feedback.
-
|
Well I am likely responsible for that change. At least I recommend them doing that change from an upstream POV. But that doesn't change the fact that upstream and downstream are different people. There were a few bugs reported on debian and on our repo here that are caused by having the units enabled by default. (I don't have the time to link them here right now but if you start at the debian changelogs/bugs you can work your way backwards) |
Beta Was this translation helpful? Give feedback.
-
|
For those interested, debian changelog: Debian FTP Changeloghttps://metadata.ftp-master.debian.org/changelogs//main/p/podman/podman_5.4.2+ds1-1_changelog Debian source commit changeloghttps://salsa.debian.org/go-team/packages/podman/-/commit/f8d52b37a66f27506fdb031fa6056b67d3894420 Longer Explanation and actual changeshttps://salsa.debian.org/go-team/packages/podman/-/commit/d86fa2475ea89ff93e73cae4d223cc24116b2eb1 |
Beta Was this translation helpful? Give feedback.
Are you talking about the debian changes? That is not us but the debian packager.
Anyhow, we have no plans to remove these units. You just have to run systemctl enable on them on your own.
There are a few problems with having them enabled by default that should be mentioned if you follow the debian bug reports but as long as you enable them intentionally it is fine.