Bug 1194630 - yast2-docker crashes because of docker-api when running a docker container
yast2-docker crashes because of docker-api when running a docker container
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: YaST Team
Jiri Srain
https://trello.com/c/wGcHH2YM
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-01-13 10:43 UTC by Knut Alejandro Anderssen González
Modified: 2022-10-13 08:24 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Alejandro Anderssen González 2022-01-13 10:43:52 UTC
Originally reported by Andriamanitra as a issue (see https://github.com/yast/yast-docker/issues/31)

Yast crashes with error:

| Details: undefined method `encode' for URI:Module

Something that is broken in docker-api (1.3.2) with Ruby3.0 which is the package we have in TW Factory repository.

https://build.opensuse.org/package/show/openSUSE:Factory/rubygem-docker-api?rev=1

As we have last version in https://download.opensuse.org/repositories/devel:/languages:/ruby:/extensions/openSUSE_Tumbleweed/ we probably could drop the package from Yast::Head and submit the package from devel:languages:ruby:extensions
Comment 1 David Diaz 2022-01-14 11:32:56 UTC
(In reply to Knut Alejandro Anderssen González from comment #0)
> Originally reported by Andriamanitra as a issue (see
> https://github.com/yast/yast-docker/issues/31)
> 
> Yast crashes with error:
> 
> | Details: undefined method `encode' for URI:Module
> 
> Something that is broken in docker-api (1.3.2) with Ruby3.0 which is the
> package we have in TW Factory repository.

@Knut means docker-api 1.13.2
Comment 2 Stephan Kulow 2022-10-13 08:24:57 UTC
Tested with https://build.opensuse.org/request/show/1010113 and then it works (it's still a strange UI, as errors are shown in their JSON form)