Bug 26109 - docker upstream has a new 18.09.9 version fixes multiple issues
Summary: docker upstream has a new 18.09.9 version fixes multiple issues
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2020-01-20 02:08 CET by Bruno Cornec
Modified: 2020-01-28 08:54 CET (History)
3 users (show)

See Also:
Source RPM: docker-18.09.9-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Bruno Cornec 2020-01-20 02:08:14 CET
docker upstream has a new 18.09.9 version fixes multiple issues
See: https://bugs.mageia.org/show_bug.cgi?id=25761

Packages have been pushed in updates_testing.

I'd like QA to validate them please.
TIA.
Comment 1 David Walser 2020-01-20 02:42:02 CET
Advisory:
----------------------------------------

The docker package has been updated to version 18.09.9, fixing several bugs.
See the upstream Changelog for details.

References:
https://github.com/docker/docker-ce/blob/v18.09.9/CHANGELOG.md
----------------------------------------

Updated packages in core/updates_testing:
----------------------------------------
docker-18.09.9-1.mga7
docker-devel-18.09.9-1.mga7
docker-fish-completion-18.09.9-1.mga7
docker-logrotate-18.09.9-1.mga7
docker-unit-test-18.09.9-1.mga7
docker-vim-18.09.9-1.mga7
docker-zsh-completion-18.09.9-1.mga7
docker-nano-18.09.9-1.mga7

from docker-18.09.9-1.mga7.src.rpm
Comment 2 Len Lawrence 2020-01-21 18:39:24 CET
Mageia7, x86_64

Installed all missing packages then updated them.
Ran elementary docker tests along the lines reported in https://bugs.mageia.org/show_bug.cgi?id=25806.

Forgot to restart docker but it appears to have been restarted automatically.

$ docker --version
Docker version 18.09.0-dev, build 039a7df

$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                        PORTS               NAMES
0fdcc8dbc6f4        hello-world         "/hello"            20 seconds ago      Exited (0) 19 seconds ago                         zen_torvalds
b43088689bfb        hello-world         "/hello"            5 minutes ago       Exited (0) 5 minutes ago                          focused_blackwell
d7a2d8943ce5        fedora:latest       "/bin/bash"         5 hours ago         Exited (255) 13 minutes ago                       vigilant_kilby

$ docker run -ti fedora:latest /bin/bash
[root@6da6a90d2361 /]# 

That adds a veth... monitor in gkrellm.

[root@6da6a90d2361 /]# dnf install vim
......
[root@6da6a90d2361 /]# vim stookie
<cut & pasted /etc/hosts - no idea about vim completion>
[root@6da6a90d2361 /]# cd
root@6da6a90d2361 ~]# ls
anaconda-ks.cfg  anaconda-post-nochroot.log  anaconda-post.log  original-ks.cfg
[root@6da6a90d2361 ~]# cd /
[root@6da6a90d2361 /]# ls
bin   dev  home  lib64       media  opt   root  sbin  stookie  tmp  var
boot  etc  lib   lost+found  mnt    proc  run   srv   sys      usr
[root@6da6a90d2361 /]# mv stookie ~
[root@6da6a90d2361 /]# cd
[root@6da6a90d2361 ~]# ls
anaconda-ks.cfg             anaconda-post.log  stookie
anaconda-post-nochroot.log  original-ks.cfg

No idea about testing the other packages; fish, zsh, logrotate, vim, nano, unit-test...
Used dnf to install ruby packages in the fedora container and ran irb, installed a gem.
No problems.
Installed stellarium but could not run it because it needs a qt5 environment to be set up.

Inspected the running container from another terminal using its nickname and then stopped it from that terminal.
$ docker stop 6da6a90d2361
6da6a90d2361

[root@6da6a90d2361 ~]# exit
$

$ docker run -it --name cowsay --hostname cowsay debian bash
root@cowsay:/# apt-get install -y cowsay fortune
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package cowsay
E: Unable to locate package fortune
root@cowsay:/#

That one is no longer valid.
This is as far as we can take this unless somebody can think of anything else.
Allotting the 64-bit OK anyway.

Whiteboard: (none) => MGA7-64-OK
CC: (none) => tarazed25

Comment 3 Thomas Andrews 2020-01-22 19:19:38 CET
Validating. Advisory in Comment 1.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update

Lewis Smith 2020-01-27 21:04:58 CET

Keywords: (none) => advisory

Comment 4 Mageia Robot 2020-01-28 08:54:08 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0032.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.