Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

composefs? Opening loopback device: open /dev/loop13: no such device or address" #2038

Closed
edsantiago opened this issue Jul 22, 2024 · 1 comment · Fixed by #2039
Closed
Assignees
Labels

Comments

@edsantiago
Copy link
Member

Started today, and only in my pet no-flake-retry PR with containers/podman#23274 cherrypicked:

# podman-remote [options] run -d -p 5517:5000 --name registry4 quay.io/libpod/registry:2.8.2 /entrypoint.sh /etc/docker/registry/config.yml
time="2024-07-22T09:47:06-05:00" level=error msg="Opening loopback device: open /dev/loop13: no such device or address"
Error: mounting storage for container cb6444e05e9623778fdca4560bd3e2f36bd3a290db18e78fb38b238d5d0c775a: loopback attach failed
# podman [options] --pull-option=enable_partial_images=true --pull-option=convert_images=true run -d -p 5072:5000 --name registry6 quay.io/libpod/registry:2.8.2
time="2024-07-22T14:30:22-05:00" level=error msg="There are no more loopback devices available."
Error: mounting storage for container a6ecfcc4d099586339e34403af393924cf1b294748d28e844a48b0be4692fdbf: loopback attach failed
  • rawhide : int podman rawhide root host sqlite
    • 07-22 15:41 in Podman pod create podman create pod with id file with network portbindings
    • 07-22 15:41 in Podman search podman search doesn't attempt HTTP if registry is not listed as insecure
  • rawhide : int remote rawhide root host sqlite [remote]
    • 07-22 11:01 in Podman search podman search attempts HTTP if registry is in registries.insecure and force secure is false
x x x x x x
int(3) podman(2) rawhide(3) root(3) host(3) sqlite(3)
remote(1)
@giuseppe giuseppe transferred this issue from containers/podman Jul 23, 2024
giuseppe added a commit to giuseppe/storage that referenced this issue Jul 23, 2024
the loopback device file could be already used/removed by another
process.  Since the process is inherently racy, just grab the next
available index and try again until it succeeds.

Closes: containers#2038

Signed-off-by: Giuseppe Scrivano <[email protected]>
giuseppe added a commit to giuseppe/storage that referenced this issue Jul 23, 2024
the loopback device file could be already used/removed by another
process.  Since the process is inherently racy, just grab the next
available index and try again until it succeeds.

Closes: containers#2038

Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe giuseppe added the jira label Jul 23, 2024
@giuseppe
Copy link
Member

thanks. Opened a PR to address it:

giuseppe added a commit to giuseppe/storage that referenced this issue Jul 23, 2024
the loopback device file could be already used/removed by another
process.  Since the process is inherently racy, just grab the next
available index and try again until it succeeds.

Closes: containers#2038

Signed-off-by: Giuseppe Scrivano <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants