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.

Sign up for GitHub

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

Jump to bottom

Add packages for Ubuntu 19.10 (Eoan Ermine) #832

Closed
1 task done
behrangsa opened this issue Oct 18, 2019 · 60 comments
Closed
1 task done

Add packages for Ubuntu 19.10 (Eoan Ermine) #832

behrangsa opened this issue Oct 18, 2019 · 60 comments

Comments

@behrangsa
Copy link

  • This is a feature request

Expected behavior

Ubuntu 19.10 packages to be available.

Actual behavior

Ubuntu 19.10 packages are not available.

Steps to reproduce the behavior

See https://download.docker.com/linux/ubuntu/dists/.
@thaJeztah thaJeztah mentioned this issue Oct 23, 2019
Closed
@Tset-Noitamotua
Copy link

After reading
THIS: https://stackoverflow.com/questions/45023363/what-is-docker-io-in-relation-to-docker-ce-and-docker-ee/57678382#57678382

AND: #833 (comment)

I wonder why Docker and Debian/Ubuntu don't put their efforts together and start providing ONE package to us users ❓

Debian/ubuntu (docker.io package)

  • ease of installation: just apt install docker.io and you are done (but you get an older version)

Docker Team (docker-ce package)

Why not give us users some LOVE ❓ and

  • provide the latest hot shhh with all the goodies with a simple apt install docker
  • stop confusion about docker.io vs docker-ce
  • use your valuable time saved from maintaining two packages to
    • spend more time with family & friends
    • do more sports
    • have more sex
    • etc. etc.

@MycroftHolmes1989
Copy link

Is it possible to pack Docker into a flatpak? That way, we don't have to badger the devs for an updated version every time Ubuntu releases a new version.

@behrangsa
Copy link
Author

behrangsa commented Nov 12, 2019 via email

@graingert
Copy link

graingert commented Nov 12, 2019 via email •
edited
Loading

@MycroftHolmes1989
Copy link

I think the easier way would be to put the entire project in OpenSUSE Build Services. It really is useful when it comes to targetting multiple distros and multiple releases.

@slashsbin
Copy link

Hey guys,
I'm curious, Isn't the docker snap another viable solution?
Isn't it a good replacement for package management and also in a cross-distribution way?
Although, I know it has the limitation of using Dockerfile inside $HOME directory.

@MycroftHolmes1989
Copy link

Hey guys,
I'm curious, Isn't the docker snap another viable solution?
Isn't it a good replacement for package management and also in a cross-distribution way?
Although, I know it has the limitation of using Dockerfile inside $HOME directory.

Not everyone is comfortable using snaps. I, for one, hate snaps. Flatpaks are a much cleaner solution, apart from PPA's.

@behrangsa
Copy link
Author

behrangsa commented Nov 14, 2019 via email

@CrazySky2121
Copy link

I like snap packages but it's not applicable for all cases. For example VS Code for using remote developing via Docker required only docker by deb and not working with docker by snap

@joaonsantos
Copy link

Is there an ETA to complete this issue?

@MycroftHolmes1989
Copy link

As far as I can tell, no. I have moved to using Podman. Docker doesn't have support for either Ubuntu 19.10 or Fedora 31. That is a deal-breaker for me.

@gdiggs
Copy link

gdiggs commented Nov 14, 2019

FWIW I've been using the 19.04 package without issues on 19.10. I installed following the directions here and replacing lsb_release -cs with disco

@behrangsa
Copy link
Author

behrangsa commented Nov 19, 2019 •
edited
Loading

FWIW I've been using the 19.04 package without issues on 19.10. I installed following the directions here and replacing lsb_release -cs with disco

That works but it is hacky. Ubuntu has 6 monthly release cycles and Docker support for new Ubuntu versions happens on the 4th or 5th month of the cycle. By the time everything is working a-okay, a new version of Ubuntu is released and we have to wait another 4-5 months for that release to be officially supported by Docker.

At least an explanation by the Docker team on what is blocking them to release a new version of Docker as soon as a new version of Ubuntu is released would be very welcome. CC: @zelahi @joeabbey

@MycroftHolmes1989
Copy link

I've given up using docker on Ubuntu just because of this reason. It is always a release behind.

@vpavic
Copy link

vpavic commented Nov 20, 2019

This has been linked already, but I'd again suggest to take a look at #833 (comment).

With Debian packages being recent enough, I've personally given up on Docker provided repositories as those have been a biggest pain while upgrading Ubuntu.

To clarify, installing docker.io and docker-compose packages on Ubuntu 19.10 gets you:

$ docker version 
Client:
 Version:           19.03.2
 API version:       1.40
 Go version:        go1.12.9
 Git commit:        6a30dfca03
 Built:             Mon Sep 16 03:56:22 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          19.03.2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.9
  Git commit:       6a30dfca03
  Built:            Wed Sep 11 22:45:55 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10-0ubuntu1
  GitCommit:        
 runc:
  Version:          spec: 1.0.1-dev
  GitCommit:        
 docker-init:
  Version:          0.18.0
  GitCommit:        
$ docker-compose version 
docker-compose version 1.21.0, build unknown
docker-py version: 3.4.1
CPython version: 3.7.5rc1
OpenSSL version: OpenSSL 1.1.1c  28 May 2019

@pofl
Copy link

pofl commented Dec 5, 2019

It's really disappointing that the get.docker.com script doesn't complain when I'm on an unsupported version (19.10 today).

@behrangsa
Copy link
Author

@zelahi what's blocking this?

@zelahi zelahi removed their assignment Dec 5, 2019
@christian-weiss
Copy link

Ok, i can tolerate that Ubuntu 19.10 is not a supported distro.

But why is the repo for Ubuntu 19.04 (disco) not having the latest docker-ce release?
Latest release is 19.03.5 (https://docs.docker.com/engine/release-notes/), but Ubuntu 19.04 repo (disco) is not providing it. Not even 19.03.4. Latest release in (disco) repo is 19.03.3.

@paillave
Copy link

The pb is that sql server is only available for ubuntu 18.04. And for anything further version, we must install it on docker... but we can't install docker on 19.10
docker became such a crucial system nowadays... it's really surprising and scary to see that ubuntu (the most popular linux distro) 19.10 is still not supported 2 month after its release and 3 months after its first beta version. Is there so much things to test and to upgrade, or ubuntu support is just one of the lasts in priorities?

@MycroftHolmes1989
Copy link

Docker CE team is trying really hard to outdate themselves. Ubuntu 20.04 LTS beta is out, and they should focus on that instead of 19.10.
For everyone who can, I would suggest using podman. I have given up hope on Docker's support for latest distros.

@testautomation
Copy link

For everyone who can, I would suggest using podman ...

Cool. @MycroftHolmes1989 thanx for the hint. I've never heart of podman before. But it really looks like worth a try. Read THIS!

https://github.com/containers/libpod
https://github.com/containers/buildah

I guess it's main downside is that it is Unix only, so on Windows you'll have to use it inside WSL or in a VM(?)

@behrangsa
Copy link
Author

behrangsa commented Dec 16, 2019 via email

@MycroftHolmes1989
Copy link

For everyone who can, I would suggest using podman ...

Cool. @MycroftHolmes1989 thanx for the hint. I've never heart of podman before. But it really looks like worth a try. Read THIS!

https://github.com/containers/libpod
https://github.com/containers/buildah

I guess it's main downside is that it is Unix only, so on Windows you'll have to use it inside WSL or in a VM(?)

Podman is really nice, and the devs are extremely quick to respond. I asked them to put their project on OBS (OpenSUSE Build Service) and just within 2 weeks, it was on there. This really helps with the timely updates.

@jonstelly
Copy link

jonstelly commented Dec 18, 2019 •
edited
Loading

To hopefully recap a bit, the distribution situation seems a bit worse than not having packages for an OS with one of the most predictable release schedules, when the release has been out for 2 months and doesn't seem to have any major changes from the previous release.

Since Ubuntu is on a 6 month release cycle, if it takes 2-3 months to get docker onto a newly GA version of Ubuntu, 50% of the 'current' lifecycle of an Ubuntu release doesn't have a clean method to install docker.

State of things:

  • Canonical has revived the docker.io apt package which is available for eoan, but latest stable is 19.03.2
  • Docker is also available via snap but that is only 18.09.9 which I'd argue is useless for development at this point unless you're still running 18.09.9 somewhere
  • It IS possible to use the script from get.docker.com for eoan. After the script runs, edit the /etc/apt/sources.list.d/docker.list and change eoan to disco, run apt update && apt install docker-ce and you're good to go. But this only seems to install docker 19.03.3 even though 19.03.5 is available
  • After running the same process from above but using the script from test.docker.com I ended up with 19.03.4 rc1. 19.03.5 isn't even available as a beta/rc for Ubuntu yet?
  • The readme from this for-linux github repository (and probably other docker documentation locations) point you to here and here for Ubuntu which only mentions support of Ubuntu up to 17.10 but links to the instructions here that end up with the same result as running the get.docker.com script

So:

  • Is docker 19.03.5 a windows-only release? If not, where/how should I get that version of the engine installed on Ubuntu (eoan, disco, anything)?
  • Is there a reason that the package channel installed from the test.docker.com script still points to an RC of 19.03.4 and not the final release or even a beta/RC of 19.03.5? Is there value there that I'm not seeing? This is different behavior than how the Docker for Desktop Edge channel works where once the release goes GA the channel is updated to that GA release until new betas start to hit the channel.
  • It feels like there are at least 4 different and uncoordinated efforts to provide documentation and delivery and none of them have the latest release of the docker engine available. How did that happen?

Some attention to cleaning this up would really help the cloud of confusion and churn you see from the community every release of Ubuntu (eoan, disco, bionic, artful).

@jonstelly jonstelly mentioned this issue Dec 19, 2019
Open
3 tasks
@behrangsa
Copy link
Author

One of the main reasons why I've not upgraded to 19.10 is lack of Docker CE. And next month Ubuntu stops providing package updates for 19.04. Until Docker publishes packages for 19.10, I guess I will be spending time in Purgatorio. 🙃

@mikeactual
Copy link

Docker 19.03.5 is available in the bionic dist location. The latest long term distribution must be a higher priority for the Docker developers than the latest distro available is. In any case I've been running Docker 19.03.05 on Ubuntu Eoan. Works fine on my dev machine. However that is a very small sample size with very limited use case coverage. Your mileage may vary but it is available if you want it.

To be clear, it's available here: https://download.docker.com/linux/ubuntu/dists/bionic/pool/stable/amd64/

@MycroftHolmes1989
Copy link

Does anyone care about this anymore? Focal Fossa release just just months away. I would suggest that Docker team should spend their effort for packaging targeting 20.04 LTS.

@jonstelly
Copy link

Does anyone care about this anymore? Focal Fossa release just just months away. I would suggest that Docker team should spend their effort for packaging targeting 20.04 LTS.

Personally, I've got the bionic docker repository working for now and the lack of 19.10 packages has taken way too long to resolve IMHO so for me it's time to take a serious look at podman and I don't really care about 19.10 or 20.04 packaging. This issue has just taken way too long to resolve and there hasn't really been any comment or acknowledgement from anyone on the project so it doesn't seem like they understand or even care.

@felicianotech
Copy link

This is still important. Getting Ubuntu 19.10 packages specifically no, but the principle here of having proper support for Ubuntu. I wouldn't want to run into the same issue again for 20.10 or 21.04.

The Docker and Moby split is still a bit confusing for me. Is there a way to create Ubuntu packages for Docker ourselves? Depending on what's possible for the build system, I'd build 3rd-party packages for Ubuntu the same way AdoptOpenJDK builds OpenJDK packages.

@mikeactual
Copy link

I've been reading around on the internet (big me, eh?) and my conclusion is that this issue is already resolved. Not the way we'd all like it to be, however. At some point Docker made the decision to only support Ubuntu LTS releases. You will only ever get the latest official Docker CE for them. Sorry, that's it.

If you want to run the official Docker CE on Ubuntu interim releases then grab the latest Ubuntu LTS packages and install them manually. This shouldn't be a huge problem. Canonical doesn't lightly make changes to subsequent releases that break existing applications. Docker CE should continue to work on the interim builds.

In looking at the mobyproject.org site someone could theoretically create Ubuntu packages from there but it would not be simple. This theoretical someone would need to become a Docker internals subject matter expert. Also any out of band packages would be unsupported and would require a whole lot of work to create. All for little or no long term gain.

Personally I'm going to quit gnashing my teeth over this and use the latest LTS official Docker CE wherever I need it.

Ciao

@jonstelly
Copy link

First, I'm not trying to argue like some internet nerd, but...

At some point Docker made the decision to only support Ubuntu LTS releases. You will only ever get the latest official Docker CE for them. Sorry, that's it.

Can you cite a source for this? Their Ubuntu installation page mentions 18.10 and 19.04 and uses lsb_release -cs when setting up the docker repository. I know sometimes their documentation lives in several places and doesn't always agree 100% from one source to the other so I don't doubt you saw that somewhere.

If you want to run the official Docker CE on Ubuntu interim releases then grab the latest Ubuntu LTS packages and install them manually. This shouldn't be a huge problem. Canonical doesn't lightly make changes to subsequent releases that break existing applications. Docker CE should continue to work on the interim builds.

I'm not a go guy, but I know dotnet core has different library dependencies from 18.04 to 19.04 and 19.10 (libcurl from 3 to 4 maybe and some others). But if they do decide to only publish packages for LTS releases, then they need to remove the non-lts repositories and change their documentation and scripts to something like the following. The current Ubuntu situation is just bad for everyone, Docker and their users.

if (Release >= 18.04)
    return "bionic"
if(Release >= 16.04)
    return "xenial"
throw "Get out of here with that old stuff!"

Personally I'm going to quit gnashing my teeth over this

Same!

@cpuguy83
Copy link
Collaborator

There's a packaging repo at https://github.com/tianon/debian-moby

But there is a bit of glue to make that happen.

I'd be down to have "official", community supported packages under the moby org, assuming there would be people to help maintain it.
Hosting for this would need to be dealt with.
It's unfortunate GH's new package repo thingy doesn't support apt.

@arkodg
Copy link

arkodg commented Jan 28, 2020

Folks the docker-ce and containerd packages should now be available on the test channel and can be installed via curl -fsSL https://get.docker.com/ | CHANNEL=test sh . These packages will be promoted to the stable channel soon after they have been verified completely.
We apologize for the delay in providing these packages and we will make sure we don't let interim releases such as Ubuntu Eoan slip in the future

@behrangsa
Copy link
Author

behrangsa commented Jan 28, 2020 via email

@brylie brylie mentioned this issue Jan 31, 2020
Merged
@ricktendo
Copy link

Files are now in the stable repo, this issue can be considered resolved.

@ljburtz
Copy link

ljburtz commented Feb 14, 2020

I dont see containerd.io in the Packages of the stable repo at https://download.docker.com/linux/ubuntu/dists/eoan/stable/binary-amd64/

@ricktendo can you clarify:

Much appreciated! Thanks!

@CrazySky2121
Copy link 

apt info containerd.io
Package: containerd.io
Version: 1.2.12-1
Priority: optional
Section: devel
Maintainer: Containerd team <help@containerd.io>
Installed-Size: 91,5 MB
Provides: containerd, runc
Depends: libc6 (>= 2.14), libseccomp2 (>= 2.4.0)
Conflicts: containerd, runc
Replaces: containerd, runc
Homepage: https://containerd.io
Download-Size: 20,1 MB
APT-Manual-Installed: yes
APT-Sources: https://download.docker.com/linux/ubuntu eoan/stable amd64 Packages
Description: An open and reliable container runtime

@paillave
Copy link

@ljburtz everything is mentioned in the updated documentation: https://docs.docker.com/install/linux/docker-ce/ubuntu/

@kobelobster
Copy link

kobelobster commented Feb 15, 2020 •
edited
Loading

I followed the exact steps to this but am still getting the errors that these packages don't exist

sudo apt-key fingerprint 0EBFCD88 returns


pub   rsa4096 2017-02-22 [SCEA]
      9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88
uid           [ unknown] Docker Release (CE deb) <docker@docker.com>
sub   rsa4096 2017-02-22 [S]`

This is in my /etc/apt/sources.list

deb [arch=amd64] https://download.docker.com/linux/ubuntu eoan stable test nightly
# deb-src [arch=amd64] https://download.docker.com/linux/ubuntu eoan stable test nightly

I did sudo apt update afterwards but still getting therse errors

ubuntu@ubuntu:~$ sudo apt-get install docker-ce docker-ce-cli containerd.io
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
However the following packages replace it:
  docker-ce-cli:amd64

E: Package 'docker-ce' has no installation candidate
E: Unable to locate package docker-ce-cli
E: Unable to locate package containerd.io
E: Couldn't find any package by glob 'containerd.io'
E: Couldn't find any package by regex 'containerd.io'

@incomingstick
Copy link

I am experiencing the same issue as @tzfrs and @ljburtz

I followed the install steps and when I try the actual install I receive the same output:

Command: sudo apt-get install docker-ce docker-ce-cli containerd.io

Reading package lists... Done
Building dependency tree
Reading state information... Done
Package containerd.io 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 'containerd.io' has no installation candidate

Omitting containerd.io from the above command results in the following output:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 docker-ce : Depends: containerd.io (>= 1.2.2-3) but it is not installable
             Recommends: aufs-tools but it is not going to be installed
             Recommends: cgroupfs-mount but it is not going to be installed or
                         cgroup-lite but it is not going to be installed
             Recommends: pigz but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

@ricktendo as it seems it cannot be installed, as containerd.io is missing from the repo, I would not consider this resolved.

@christian-weiss
Copy link

containerd.io is not available in stable but in test and nightly
1.2.12-1
1.2.10-2
1.2.10-1

sources:
deb [arch=amd64] https://download.docker.com/linux/ubuntu eoan stable test nightly
run:

sudo apt-get update
apt-cache policy containerd.io

@iav
Copy link

iav commented Feb 21, 2020

related docker/docs#10308

@Dominic-Mayers
Copy link

Dominic-Mayers commented Feb 22, 2020 •
edited
Loading

I believe in https://download.docker.com/linux/ubuntu/dists repository, containerd.io can be replaced with containerd (without the io extension). For example, in https://askubuntu.com/a/1212388/456438 , I replaced containerd.io with containerd in the standard instruction https://docs.docker.com/install/linux/docker-ce/ubuntu/ to install docker-ce and it worked.

@behrangsa behrangsa mentioned this issue Feb 23, 2020
Closed
1 task
@behrangsa
Copy link
Author

Hi all,

Please vote for #940.

Thanks.

@b0le
Copy link

b0le commented Feb 23, 2020

@MaharishiCanada the containerd package (without the .io suffix) is the Debian/Ubuntu package maintainers' version and is the dependency of Debian/Ubuntu's docker.io package. Either install the Ubuntu-supplied docker.io package and its dependencies, or install docker-ce, docker-ce-cli, and containerd.io from Docker's own repository.

Do note that as of February 23, 2020, the containerd.io package is still missing from Docker's stable repository for Ubuntu 19.10 (see the Packages file at https://download.docker.com/linux/ubuntu/dists/eoan/stable/binary-amd64/) and installation will fail as a result of this.

@Dominic-Mayers
Copy link

Dominic-Mayers commented Feb 23, 2020 •
edited
Loading

@b0le Yes the package containerd.io that you refer to is maintained by the Containerd team whereas the package containerd that I refer to is maintained by the Ubuntu Developers. The package containerd.io mentions that it can be used where containerd and runc are required, but the converse is not affirmed. So, my suggestion to use containerd (with runc) as a replacement for containerd.io is not robust, even though it apparently works.
On the other hand, the suggestion of https://askubuntu.com/a/1190896/456438 to install directly some version of containerd.io , which was not tested in the package, might not be better. There is nothing magical about the fact that it comes from the same team.

@melvinmajor
Copy link

melvinmajor commented Feb 26, 2020 •
edited
Loading

Personally, I had the issue with no installation candidate of containerd.io for Ubuntu Server 19.10 LTS.
The workaround is actually to specify manually an older version of Ubuntu (19.04) which will give us all installation candidate... That's a shame that we are obliged to work like that in order to have Docker-CE installed correctly and usable.

sudo add-apt-repository \
   "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
   disco \
   stable"

@mikeactual
Copy link

The cleanest way that I've found to do this is to download these files:

https://download.docker.com/linux/ubuntu/dists/eoan/pool/stable/amd64/docker-ce-cli_19.03.6~3-0~ubuntu-eoan_amd64.deb

https://download.docker.com/linux/ubuntu/dists/eoan/pool/stable/amd64/docker-ce_19.03.6~3-0~ubuntu-eoan_amd64.deb

https://download.docker.com/linux/ubuntu/dists/eoan/pool/test/amd64/containerd.io_1.2.12-1_amd64.deb

Then run these commands in terminal:

sudo dpkg -i containerd.io_1.2.12-1_amd64.deb
sudo dpkg -i docker-ce-cli_19.03.63-0ubuntu-eoan_amd64.deb
sudo dpkg -i docker-ce_19.03.63-0ubuntu-eoan_amd64.deb

I wouldn't run this in production but it works on both eoan and focal.

Screen Shot 2020-03-02 at 1 35 51 AM

@Barbiero
Copy link

Barbiero commented Mar 5, 2020

For those following this thread, it seems that containerd.io is FINALLY available for Eoan on the stable branch. This means that the get.docker.com convenience script now works properly!

and with 50 days to spare before the release of 20.04 😅

@thaJeztah
Copy link
Member

Thanks; yes, a regression was found in the containerd.io 1.2.12 version, and we had to temporarily roll back those packages; unfortunately no prior releases of the package were done for Ubuntu Eoan, so there were no packages for it during that time.

containerd.io 1.2.13 is now up, so closing this

@paillave
Copy link

paillave commented Mar 5, 2020

Thanks a lot Sebastian @thaJeztah. Was this delay due to some issues that needed to be solved also for the next release of Ubuntu 20.04, or will we have to face the same delay to use docker on the next ubuntu LTS?

@graingert
Copy link

graingert commented Mar 5, 2020 via email

@LouisMT LouisMT mentioned this issue Sep 19, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests