http://bugzilla.opensuse.org/show_bug.cgi?id=1204983
Bug ID: 1204983 Summary: Unable to create distrobox with tumbleweed image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner@suse.de Reporter: logan.clarke@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: ---
Created attachment 862623 --> http://bugzilla.opensuse.org/attachment.cgi?id=862623&action=edit Output of "docker logs tumbleweed"
Distrobox fails on the Installing basic packages... step when using the Tumbleweed image.
Operating System: openSUSE Tumbleweed 20221030 Kernel Version: 6.0.5-1-default (64-bit) Graphics Platform: X11 Processors: 12 � AMD Ryzen 5 5600G with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: RENOIR Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550M DS3H AC
Distrobox version: 1.4.1 Docker version: 20.10.17-ce, build a89b84221c85
--- $ distrobox create -n tumbleweed Creating 'tumbleweed' using image registry.opensuse.org/opensuse/tumbleweed:latest [ OK ] Distrobox 'tumbleweed' successfully created. To enter, run:
distrobox enter tumbleweed ---
--- $ distrobox list ID | NAME | STATUS | IMAGE 907e89fe5168 | tumbleweed | exited | registry.opensuse.org/opensuse/tumbleweed:latest ---
--- $ distrobox enter tumbleweed Container tumbleweed is not running. Starting container tumbleweed run this command to follow along:
docker logs -f tumbleweed
Starting container... [ OK ] Installing basic packages... Warning: program compiled against libxml 210 using older 209 Warning: program compiled against libxml 210 using older 209 Warning: program compiled against libxml 210 using older 209 Warning: program compiled against libxml 210 using older 209 Error: An error occurred ---
Last entry in docker logs -f tumbleweed (full logs attached)
--- + zypper install -y Mesa-dri libvulkan1 libvulkan_intel libvulkan_radeon zypper: symbol lookup error: /lib64/libcurl.so.4: undefined symbol: nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation + '[' 127 -ne 0 ']' + printf 'Error: An error occurred\n' Error: An error occurred ---
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c1
Luciano Santos luc14n0@opensuse.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |luc14n0@opensuse.org Component|Containers |Upgrade Problems Found By|--- |Community User Assignee|containers-bugowner@suse.de |screening-team-bugs@suse.de QA Contact|qa-bugs@suse.de |jsrain@suse.com
--- Comment #1 from Luciano Santos luc14n0@opensuse.org --- Changing "Component" from "Container" to "Upgrade Problems".
Two users in openSUSE support IRC/Matrix room ran into the same issue. They had their Tumbleweed systems out of date. One installed libcurl-devel before hitting that error and the other installed development tools, which must have pulled cURL in.
In both cases thing got back to normal after downloading:
http://download.opensuse.org/tumbleweed/repo/oss/x86_64/libnghttp2-14-1.50.0...
And manually upgrading with:
# rpm -U libnghttp2-14-1.50.0-1.1.x86_64.rpm
One of them tried `zypper in` but got the error:
el archivo /usr/lib64/libnghttp2.so.14 de la instalaci�n de libnghttp2-14-1.50.0-1.1.x86_64 entra en conflicto con el archivo del paquete libnghttp2-14-1.48.0-1.1.x86_64
Something like "the file /usr/lib64/libnghttp2.so.14 from the installation of libnghttp2-14-1.50.0-1.1.x86_64 conflics with the file from the libnghttp2-14-1.48.0-1.1.x86_64 package"
Which is odd because the nghttp2 package hasn't changed in a month or so, as we can see there, the difference is only two rebuilds away from each other. Then libnghttp2-14 doesn't seem to be the problem here.
Since my Tumbleweed system died on me last week and it's still in the emergency room trying to bring it back to life, I can't do much to help troubleshooting this bug, though.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c2
--- Comment #2 from Luciano Santos luc14n0@opensuse.org --- This may not actually fit in "Upgrade Problems" component, please some correct me if so.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c3
--- Comment #3 from Logan Clarke logan.clarke@gmail.com --- (In reply to Luciano Santos from comment #1)
Changing "Component" from "Container" to "Upgrade Problems".
Two users in openSUSE support IRC/Matrix room ran into the same issue. They had their Tumbleweed systems out of date. One installed libcurl-devel before hitting that error and the other installed development tools, which must have pulled cURL in.
In both cases thing got back to normal after downloading:
http://download.opensuse.org/tumbleweed/repo/oss/x86_64/libnghttp2-14-1.50.0...
And manually upgrading with:
# rpm -U libnghttp2-14-1.50.0-1.1.x86_64.rpm
One of them tried `zypper in` but got the error:
el archivo /usr/lib64/libnghttp2.so.14 de la instalaci�n de libnghttp2-14-1.50.0-1.1.x86_64 entra en conflicto con el archivo del paquete libnghttp2-14-1.48.0-1.1.x86_64
Something like "the file /usr/lib64/libnghttp2.so.14 from the installation of libnghttp2-14-1.50.0-1.1.x86_64 conflics with the file from the libnghttp2-14-1.48.0-1.1.x86_64 package"
Which is odd because the nghttp2 package hasn't changed in a month or so, as we can see there, the difference is only two rebuilds away from each other. Then libnghttp2-14 doesn't seem to be the problem here.
Since my Tumbleweed system died on me last week and it's still in the emergency room trying to bring it back to life, I can't do much to help troubleshooting this bug, though.
I'm not sure that is my issue...
`zypper info libnghttp2-14`
``` Information for package libnghttp2-14: -------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : libnghttp2-14 Version : 1.50.0-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 171.3 KiB Installed : Yes (automatically) Status : up-to-date Source package : nghttp2-1.50.0-1.1.src Upstream URL : https://nghttp2.org/ Summary : Shared library for nghttp2 Description : Shared C libraries for implementation of Hypertext Transfer Protocol version 2. ```
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c4
--- Comment #4 from Luciano Santos luc14n0@opensuse.org ---
Which is odd because the nghttp2 package hasn't changed in a month or so, as we can see there, the difference is only two rebuilds away from each other. Then libnghttp2-14 doesn't seem to be the problem here.
I should correct myself here. My thinking was a wrong (I swear I'm feeling less smart without my Linux box).
A month ago the nghttp2 package got updated from 1.49.0 to 1.50.0 that brought the new symbol nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation. So for the cases I pointed out, where users didn't update their Tumbleweed systems and had a libnghttp2-14 version previous to 1.50.0, it makes sense Zypper throwing that error because libcurl4 requires libnghttp2.so.14()(64bit) provided by libnghttp2-14.
I might be wrong here, but since libcurl4 is depending on a new symbol introduced by nghtt2 1.50.0, there should've been introduced a new check for that specific symbol in there configure script, something like [1].
[1] https://github.com/curl/curl/blob/c0b24c93a99f5c3f97aa7c8377a7bcb7dbde8c1c/c...
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c5
--- Comment #5 from Luciano Santos luc14n0@opensuse.org --- (In reply to Logan Clarke from comment #3)
I'm not sure that is my issue...
`zypper info libnghttp2-14`
Information for package libnghttp2-14: -------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : libnghttp2-14 Version : 1.50.0-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 171.3 KiB Installed : Yes (automatically) Status : up-to-date Source package : nghttp2-1.50.0-1.1.src Upstream URL : https://nghttp2.org/ Summary : Shared library for nghttp2 Description : Shared C libraries for implementation of Hypertext Transfer Protocol version 2.
Well, now that's odd. The correct nghttp2 version is there and libcurl4 is still throwing a undefined symbol error.
Could do try pulling the latest Tumbleweed image and create a new container please?
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c6
--- Comment #6 from Luciano Santos luc14n0@opensuse.org ---
Could do try pulling the latest Tumbleweed image and create a new container please?
Could you try pulling the latest Tumbleweed image and create a new container please?
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c7
Imo Hester vortex@z-ray.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vortex@z-ray.de
--- Comment #7 from Imo Hester vortex@z-ray.de --- Created attachment 862752 --> http://bugzilla.opensuse.org/attachment.cgi?id=862752&action=edit distrobox microsos kde
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c8
--- Comment #8 from Imo Hester vortex@z-ray.de --- Sorry, never mind my attachment. It appears I just had a broken setup as I migrated my existing Tumbleweed home to MicroOS and something broke along the way. With a clean home and a clean fresh user everything works as expected.
my bad :(
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c9
--- Comment #9 from Logan Clarke logan.clarke@gmail.com --- (In reply to Luciano Santos from comment #6)
Could you try pulling the latest Tumbleweed image and create a new container please?
Well that worked. Thanks.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204983 http://bugzilla.opensuse.org/show_bug.cgi?id=1204983#c10
Luciano Santos luc14n0@opensuse.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #10 from Luciano Santos luc14n0@opensuse.org --- Very well. I feel this is one of those few transient issues where it may never happens again. Closing it.
-
bugzilla_noreply＠suse.com