-
Notifications
You must be signed in to change notification settings - Fork 3k
Closed
Labels
flakesFlakes from Continuous IntegrationFlakes from Continuous Integrationkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.remoteProblem is in podman-remoteProblem is in podman-remotestale-issue
Description
Looks like a race condition. Symptom is:
$ podman-remote [options] start --attach test
Error: unable to start container b1ce2aadbf58178fe75cb41da71dd0bf8e4b53cea21029da2a5c4d08a7f32da7: can only attach to created or running containers - currently in state stopped: container state improperPodman run restart containers [It] Podman start after successful run
- gce_instance:fedora : int remote fedora-33 root host
- gce_instance:prior-fedora : int remote fedora-32 root host
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
flakesFlakes from Continuous IntegrationFlakes from Continuous Integrationkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.remoteProblem is in podman-remoteProblem is in podman-remotestale-issue