Podman: Can't start a container while a push operation is in progress
Was trying to push a container image to quay.io and in a separate terminal I tried to start a container based on it. The start operation blocked without any apparent feedback in the terminal or the journal. Cancelling the push allowed me to create it.
Some kind of locking I suppose? If so, seems like they should be using shared lock?
jlebon
All 10 comments
I wonder if this is the c/storage locking that @saschagrunert has been trying to work around with https://github.com/containers/storage/pull/473
mheon
on 29 Feb 2020
If starting containers does not need write access to layers then we could solve it with https://github.com/containers/storage/pull/473. If not, then we can still solve this issues with layer-wise storage locking.
saschagrunert
on 29 Feb 2020
A friendly reminder that this issue had no activity for 30 days.
![github-actions[bot] picture](https://avatars2.githubusercontent.com/in/15368?v=4&s=40)
github-actions[bot]
on 31 Mar 2020
This is still being worked on.
rhatdan
on 31 Mar 2020
@saschagrunert Still working on this?
rhatdan
on 9 Jun 2020
Yep this still depends on https://github.com/containers/storage/pull/473
saschagrunert
on 9 Jun 2020
Still waiting. @nalind WDYT, Can we finally get the containers/storage update?
rhatdan
on 10 Sep 2020
A friendly reminder that this issue had no activity for 30 days.
github-actions[bot]
on 8 Nov 2020
We are getting closer on this.
rhatdan
on 10 Nov 2020
Sadly still in a holding pattern on this.
rhatdan
on 24 Dec 2020
Related issues
cevich
路
69Comments
juansuerogit
路
51Comments
kallisti5
路
49Comments
markstos
路
148Comments
jlebon
路
58Comments