Bug: Restarting rootless containers with published ports fails (coredump) #6089
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When running a container with a published port (rootless) like so:
And restarting the container afterwards:
One will get an error like:
and the container will be stopped. Starting the container via
start
afterwards works fine. A coredump will be created via systemd:information
The text was updated successfully, but these errors were encountered: