Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker-ce package is missing for Ubuntu "Disco Dingo" 19.04 x86_64 #533

Closed
denji opened this issue Dec 25, 2018 · 15 comments

Comments

Projects
None yet
8 participants
@denji
Copy link

commented Dec 25, 2018

Ubuntu 19.04 (Disco Dingo) released https://lists.ubuntu.com/archives/ubuntu-announce/2019-April/000243.html

18.10 (Cosmic) problem tags edge/nightly:

https://docs.docker.com/install/linux/docker-ce/ubuntu/#set-up-the-repository
builds from the edge or test repositories as well

https://download.docker.com/linux/ubuntu/dists/cosmic/pool/
nightly
test

$ lsb_release -rdc
Description:	Ubuntu 19.04
Release:	19.04
Codename:	disco
@DeeDeeG

This comment has been minimized.

Copy link

commented Mar 17, 2019

There are now nightly build for disco: https://download.docker.com/linux/ubuntu/dists/disco/pool/
And there are stable builds for cosmic: https://download.docker.com/linux/ubuntu/dists/cosmic/pool/

I personally am using the cosmic stable builds on disco, and they are working for me.

@denji denji closed this Mar 17, 2019

@edno

This comment has been minimized.

Copy link

commented Apr 23, 2019

docker-ce and docker-ce-cli packages are still missing for Disco stable builds

@seemethere

This comment has been minimized.

Copy link
Member

commented Apr 23, 2019

@edno Stable builds for Disco will be added with the release of Docker CE 19.03.0,

If you'd like to try out the builds you can install them through our test channel:

curl -fsSL get.docker.com | CHANNEL=test sh
@gabrielcalderon

This comment has been minimized.

Copy link

commented Apr 23, 2019

@seemethere Thanks for the news!

@brylie

This comment has been minimized.

Copy link

commented May 22, 2019

I see this issue was closed, but am experiencing it with 19.04. I have followed the official installation instructions as well as a Medium article, but I see no installation candidate:

apt-cache policy docker-ce
docker-ce:
  Installed: (none)
  Candidate: (none)
  Version table:
@brylie

This comment has been minimized.

Copy link

commented May 22, 2019

I.e. this issue should probably closed once the official packages are released.

@bdecarne

This comment has been minimized.

Copy link

commented May 22, 2019

I used :

sudo apt install docker.io
@brylie

This comment has been minimized.

Copy link

commented May 22, 2019

The docker.io Ubuntu package looks fairly recent, at 18.09:
https://packages.ubuntu.com/disco/docker.io

However, the official install instructions for Docker CE say to uninstall docker.io:

https://docs.docker.com/install/linux/docker-ce/ubuntu/

Running the curl -fsSL get.docker.com | CHANNEL=test sh command installs Docker 19.03 for me.

@gitowiec

This comment has been minimized.

Copy link

commented Jun 11, 2019

On Disco Dingo I did (as manual says)

sudo add-apt-repository
"deb [arch=amd64] https://download.docker.com/linux/ubuntu
$(lsb_release -cs)
stable"
Then
sudo apt-get install docker-ce docker-ce-cli containerd.io

And all I got is these errors:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'docker-ce' has no installation candidate
E: Unable to locate package docker-ce-cli

What to do?

@gabrielcalderon

This comment has been minimized.

Copy link

commented Jun 11, 2019

@gitowiec As state a few comments before:

"Stable builds for Disco will be added with the release of Docker CE 19.03.0."

This release isn't out yet. Ubuntu did publish 18.09 with package "docker.io", I used that one and works fine so far. If you are looking for a long-term solution I would wait for the 19.03 Docker-CE release.

@gitowiec

This comment has been minimized.

Copy link

commented Jun 11, 2019

I edited the entry in /etc/apt/sources.list and switched from
deb [arch=amd64] https://download.docker.com/linux/ubuntu disco stable
to
deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable
and I got error:

groupadd: cannot lock /etc/group; try again later.
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 10
Processing triggers for systemd (240-6ubuntu5) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

What should I do?

@gabrielcalderon

This comment has been minimized.

Copy link

commented Jun 11, 2019

@gitowiec You can't install the Bionic package in a Disco Dingo release... Revert that change you just did and do this:

apt update && apt install docker.io

This will install Docker 18.09.

@gitowiec

This comment has been minimized.

Copy link

commented Jun 11, 2019

Unfortunately I got another problem

sudo apt install docker.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
bridge-utils ubuntu-fan
Suggested packages:
ifupdown debootstrap docker-doc rinse zfs-fuse | zfsutils
The following packages will be REMOVED:
docker-ce-cli
The following NEW packages will be installed:
bridge-utils docker.io ubuntu-fan
0 upgraded, 3 newly installed, 1 to remove and 40 not upgraded.
Need to get 30.8 MB of archives.
After this operation, 85.9 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://archive.ubuntu.com/ubuntu disco/main amd64 bridge-utils amd64 1.6-2ubuntu1 [30.5 kB]
Get:2 http://archive.ubuntu.com/ubuntu disco/universe amd64 docker.io amd64 18.09.5-0ubuntu1 [30.7 MB]
Get:3 http://archive.ubuntu.com/ubuntu disco/main amd64 ubuntu-fan all 0.12.12 [34.6 kB]
Fetched 30.8 MB in 3s (8930 kB/s)
Preconfiguring packages ...
(Reading database ... 200640 files and directories currently installed.)
Removing docker-ce-cli (5:18.09.63-0ubuntu-bionic) ...
Selecting previously unselected package bridge-utils.
(Reading database ... 200452 files and directories currently installed.)
Preparing to unpack .../bridge-utils_1.6-2ubuntu1_amd64.deb ...
Unpacking bridge-utils (1.6-2ubuntu1) ...
Selecting previously unselected package docker.io.
Preparing to unpack .../docker.io_18.09.5-0ubuntu1_amd64.deb ...
Unpacking docker.io (18.09.5-0ubuntu1) ...
Selecting previously unselected package ubuntu-fan.
Preparing to unpack .../ubuntu-fan_0.12.12_all.deb ...
Unpacking ubuntu-fan (0.12.12) ...
Setting up docker.io (18.09.5-0ubuntu1) ...
Installing new version of config file /etc/init.d/docker ...
Installing new version of config file /etc/init/docker.conf ...
Adding group docker' (GID 132) ... groupadd: cannot lock /etc/group; try again later. addgroup: /sbin/groupadd -g 132 docker' returned error code 10. Exiting.
dpkg: error processing package docker.io (--configure):
installed docker.io package post-installation script subprocess returned error exit status 1
Setting up bridge-utils (1.6-2ubuntu1) ...
Setting up ubuntu-fan (0.12.12) ...
Created symlink /etc/systemd/system/multi-user.target.wants/ubuntu-fan.service → /lib/systemd/system/ubuntu-fan.service.
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (240-6ubuntu5) ...
Errors were encountered while processing:
docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)

@DeeDeeG

This comment has been minimized.

Copy link

commented Jun 11, 2019

Sorry everyone if this is a bit off-topic.

@gitowiec This appears to be the problem:

Adding group docker' (GID 132) ... groupadd: cannot lock /etc/group; try again later. addgroup: /sbin/groupadd -g 132 docker' returned error code 10. Exiting.

Specifically:

groupadd: cannot lock /etc/group

You should have permission to edit that file, since you are using sudo (sudo apt install). Maybe you can run this to get some clues as to what is going on?: sudo lsof +D /etc (lsof lists open files and tells you details of why they are open. Should show you why /etc/group is open and in-use.)

[Edit to add source suggesting to run lsof +D /etc: https://ubuntuforums.org/showthread.php?t=2209632&p=12955067#post12955067 ]

Also, you might try simply rebooting your computer and trying again, since this may close the program tying up /etc/group.

There is also a stackoverflow answer suggesting to do this: sudo mount -o remount,rw /
source: https://superuser.com/a/820189

You can try that if none of the other things work.

@gitowiec

This comment has been minimized.

Copy link

commented Jun 11, 2019

Thanks for fast response. I think the problem is my Ubuntu installation which is not quite full fledged installation. I made it on usb from live cd with mkusb... I think it just binds /etc from the "cdrom" partition which is read only... I wanted go shortcut but instead I ended with double work to do because now I have to begin from the start and make full install...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.