Comment # 12 on bug 1042877 from
(In reply to Flavio Castelli from comment #11)
> (In reply to Andreas Stieger from comment #10)
> > Containers team, can you confirm that the openSUSE docker images reference
> > home:Ledest:devel for go? And if so correct the situation?
> 
> The openSUSE official images for Docker only reference the official openSUSE
> repositories:
> 
> # | Alias          | Name           | Enabled | GPG Check | Refresh
> --+----------------+----------------+---------+-----------+--------
> 1 | non-oss        | NON-OSS        | Yes     | ( p) Yes  | Yes    
> 2 | oss            | OSS            | Yes     | ( p) Yes  | Yes    
> 3 | oss-update     | OSS Update     | Yes     | ( p) Yes  | Yes    
> 4 | update-non-oss | Update Non-Oss | Yes     | ( p) Yes  | Yes  
> 
> 
> The home:Ledest:devel repository has been added by the user. I assume zypper
> is installing the "go" package from there because 1) go is not installed
> inside of the image and 2) the user repo has a more recent version of it.

I agree. The output of the gitlab job shows that the repository has been added
on-top of the openSUSE images:

$ zypper addrepo $REPOS_BASE/$CARGO_REPO/$RELEASE/$CARGO_REPO.repo
Adding repository 'home:Ledest:devel (openSUSE_Leap_42.2)' [......done]
Repository 'home:Ledest:devel (openSUSE_Leap_42.2)' successfully added

> @valentin: could it be something similar with
> https://github.com/openSUSE/docker-containers/issues/57 ?

They look similar, but issue #57 doesn't add another repository.


You are receiving this mail because: