Zypper install stays hanging "Reading installed packages" inside system container - sysbox 0.6.1
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Hello,
It's my first time writing an issue, so if I miss any important information in here just let me know, I'll be glad to provide it.
I have a system container that I'm running using the new sysbox version 0.6.1.
It's a opensuse leap based container, version 15.2. In this container I'm trying to install some packages using zypper, however when I perform any install commands it hangs while "Reading installed packages". On the previous version I had no problem doing this.
I have searched on opensuse forums for a solution to this , however what I found does not fit my scenario:
- One of the solution was to delete the lock file from zypper and perform the command again, but I have no lock file.
- Other solutions were based on restarts and some problems related with the usage of the GUI installer which I don't have as well.
Also thought it could be related with some network issues but inside this container I'm able to retrive data from website like google or perform wget commands on resources available on repositories.
Given this I'm a little bit lost on what else to try since I'm not sure where to look more to try and find the issue.
Thanks for your help in advance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No project files or tests are identified in the report. Start by reproducing the zypper install in an openSUSE Leap 15.2 system container on Sysbox 0.6.1 and collect diagnostics at the “Reading installed packages” step, then compare with the previous version. Done means identifying a reproducible Sysbox regression or documenting the evidence needed to narrow it down.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100