https://bugzilla.suse.com/show_bug.cgi?id=1222078 https://bugzilla.suse.com/show_bug.cgi?id=1222078#c1 Alexandre Vicenzi <alexandre.vicenzi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(georg.pfuetzenreu | |ter@suse.com) Assignee|containers-bugowner@suse.de |alexandre.vicenzi@suse.com CC| |alexandre.vicenzi@suse.com, | |containers-bugowner@suse.de | |, | |georg.pfuetzenreuter@suse.c | |om --- Comment #1 from Alexandre Vicenzi <alexandre.vicenzi@suse.com> --- libcontainers-common has no %config(noreplace) for /etc/containers/storage.conf, so in theory, it will replace the file. libcontainers-common and podman should always be in sync, they might have different release cycles, but the config should work, if not, that is a bug. Given the nature of Tumbleweed, podman has many release updates, so there's no real guarantee that the old storage.conf is compatible with a new release. I'm not quite sure what behavior you are expecting, could you clarify? Should we always replace storage.conf and ensure podman works with libcontainers-common? This is the current scenario. Should storage.conf not be replaced if there are custom changes? Should we update libcontainers-common more frequently? -- You are receiving this mail because: You are on the CC list for the bug.