Please provide repo for docker-ce on Fedora 30.

[jhford]

• This is a bug report
• This is a feature request
• I searched existing issues before opening this one

The Docker-CE Fedora repository is the recommended way to install Docker CE on Fedora. It has many benefits over installing from a package or any other method.

Fedora also releases a new version every six months. The Fedora repository also takes a very long time to become ready after the release of a new version, with many issues being opened after each recent Fedora is release.

Fedora has officially branched Version 30 today and might have a beta release on March 26.

I'm filing this issue to hopefully put this task on the radar, so that there might be a repository set up in time for the Fedora 30 release on April30

Release Schedule: https://fedoraproject.org/wiki/Releases/30/Schedule#Key_Milestones

[favadi]

There is test/nightly repository available for Fedora 30, but broken because containerd package is not available. Do we have plan to fix it soon?

[claysauruswrecks]

I was able to twerkaround by downloading the RPMs directly from:
https://download.docker.com/linux/fedora/30/x86_64/test/Packages/

sudo dnf install -y containerd
sudo dnf install -y ./docker-ce-cli-19.03.0-1.1.beta1.fc30.x86_64.rpm
sudo rpm -i --nodeps ./docker-ce-19.03.0-1.1.beta1.fc30.x86_64.rpm

[wohlben]

its technically also possible to just install the fedora29 versions by hardcoding the $releasever to 29 in the repository file (/etc/yum.repos.d/docker-ce.repo)

should only be done temporarily for one installation as it will create issues with updates later on.

[docker-ce-stable]
name=Docker CE Stable - $basearch
# baseurl=https://download.docker.com/linux/fedora/$releasever/$basearch/stable 
baseurl=https://download.docker.com/linux/fedora/29/$basearch/stable
enabled=1
gpgcheck=1
gpgkey=https://download.docker.com/linux/fedora/gpg
 ``

[bweston92]

Still struggling to get it working just from the docs though. https://docs.docker.com/install/linux/docker-ce/fedora/

[wohlben]

the documentation clearly states that fedora 28 and 29 are the only supported versions at the moment @bweston92 .

either wait or use a workaround as we did.

[bweston92]

@wohlben you're correct, sorry I skipped straight past that and started doing my usual workflow of copy and pasting the commands I usually take from the page.

[xarbit]

all you need:

sudo dnf config-manager --set-enabled docker-ce-test

you can also disable the stable branch if you get annoyed by the dnf ignore warning.

sudo dnf config-manager --set-disabled docker-ce-stable

thats what I used after upgrading to Fedora 30 from 29 using dnf.

[mhitza]

@jscurtu If you already had previously installed the packages, because containerd.io is missing from both test and nightly

[xarbit]

@mhitza right.. didnt think of that one thanks. 👍

[claysauruswrecks]

[ggobbe]

Is there something still blocking stable docker packages for Fedora 30?
What needs to be changed/updated to provide these packages?

[seemethere]

Yup there is a plan to release containerd packages for Fedora 30 soon, will update on a timeline but expect it within the next couple of weeks.

[claysauruswrecks]

@cyfrost - I mean, it's not like you can't speed up open source projects by paying people money to work on things you find important.

[Pazns]

@claysauruswrecks
Well, we are talking about Docker Inc., which is no poor bearded dude in a basement.
Either, Fedora is no weird copycat distro lying in a dark corner of internet.
While I agree with the idea, I don't think it applies here.

However, I honestly don't know how much work it would have been to port the then-current version of the docker ecosystem ahead of time for the release of Fedora 30.
I think I may not realise what it involves.

[dbronecki]

For now I'm using moby-engine package on Fedora 30. It seems to be working perfectly fine as Docker CE replacement.

[jhford]

I've filed #665 for Fedora 31 preemptively today.

[basvandenbrink]

I agree with @Pazns and @dbronecki. We are now kinda forced to seek alternatives (and there are multiple nowadays) only because the packages are not released on time...

[luisnabais]

I think this delay is related to the way Fedora and Red Hat are running away from Docker and directing to Podman, Buildah, Skopeo and Kubernetes/Openshift.

[Pazns]

@luisnabais Interesting.
Is there any official "sources" about this ?

[luisnabais]

@Pazns I guess this is just an interpretation.

I've noticed on the last versions of Fedora, the Docker official packages for each latest version of Fedora are released at least some weeks after the Fedora final release, when on Debian 10 and Ubuntu 19.04 they are released early, even before the final version of the Linux distribuition is released.
Also, the number of articles on official Red Hat and Fedora related websites about using Podman/Buildah/Skopeo or containers without Docker are really high.

Examples:
https://developers.redhat.com/blog/2018/11/20/buildah-podman-containers-without-daemons/
https://developers.redhat.com/blog/2018/11/29/managing-containerized-system-services-with-podman/
https://developers.redhat.com/blog/2019/02/21/podman-and-buildah-for-docker-users/

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/finding_running_and_building_containers_without_docker

https://fedoramagazine.org/fedora-classroom-building-container-images-with-buildah/

[jpcaparas]

While moby-engine works for some people, it does not for me. One of my containers is maxing out system resources and grinding my machine to a halt (even with cgroups slices).

I had to use the the containerd.io package from F28 (to quell dependency issues) and installed the docker and docker-cli test builds. Problem solved.

The steps I followed are below:
https://gist.github.com/jpcaparas/cf4db5230796b04cccf38c39bb674a12

[Pazns]

@luisnabais
Thanks for the resources!

@jpcaparas
Try using docker-ce from Docker repo with a - -releasever=29 option.

[aric49]

@luisnabais
Thanks for the resources!

@jpcaparas
Try using docker-ce from Docker repo with a - -releasever=29 option.

Worked for me on Fedora 30. When the release of docker drops for Fedora 30, will dnf automatically upgrade the fedora 29 version in favor of Fedora 30 stable?

[rickatnight11]

Yes, as the Fedora 30 release will also be a newer version of the package.

It works the same way if you upgrade an existing Fedora install with an existing Docker installation to a new release. Your installed Docker continues to function and seamlessly receives updates as soon as the new repo becomes available.

[aric49]

@rickatnight11 -- Fantastic. I think that should be added to the Docker documentation at: https://docs.docker.com/install/linux/docker-ce/fedora/ wording to the effect of:

At this time newer versions of Fedora may not be supported right away. To install Docker for an older release of Fedora use DNF with a lower Fedora release number:

sudo dnf install --releasever=29 docker-ce docker-ce-cli containerd.io

Or something like that. Thoughts?

[stklcode]

I think that should be added to the Docker documentation [...] Thoughts?

It is not officially supported in terms of a stable, tested release. So why should a hack like this (which is the first thing that comes to my mind to deal with the "problem" anyway) be mentioned in the official docs?

It's a calculated risk to install from the previous release's repo. It worked well in the past and so it does with F29/30 and that's probably fine for most cases. But has to be carefully considered before updating or setting up productive systems (applies to various other repos and systems as well)

[mccheesy]

Yup there is a plan to release containerd packages for Fedora 30 soon, will update on a timeline but expect it within the next couple of weeks.

Any update on this?

[rux616]

I think that should be added to the Docker documentation [...] Thoughts?

It is not officially supported in terms of a stable, tested release. So why should a hack like this (which is the first thing that comes to my mind to deal with the "problem" anyway) be mentioned in the official docs?

It's a calculated risk to install from the previous release's repo. It worked well in the past and so it does with F29/30 and that's probably fine for most cases. But has to be carefully considered before updating or setting up productive systems (applies to various other repos and systems as well)

I totally agree that it's a calculated risk, but I would also argue that in the absence of on-time release support, this verbiage should be added to the official docs. That being said, I believe it should also include a very plainly-stated warning that this is indeed a hack and should be taken with all caveats therein, for example that you shouldn't do this for anything critical or production-related, nor should you expect it to work 100% of the time. (And also that you are effectively going 'off book' at that point, so official support is going to be non-existent and even unofficial support will likely be thin.)

[Nhoya]

Any news on that?

[nicolasmure]

As stated by @dbronecki [1], and briefly explained in an other thread [2], fedora no longer ships docker-ce package but ships moby-engine instead, which provides the docker binary and daemon [3].

---

[1] #600 (comment)
[2] projectatomic/docker#287 (comment)
[3] https://src.fedoraproject.org/rpms/moby-engine

[stklcode]

Just to mention, moby-engine ships 18.06 with the stable package as of today and 18.09 for testing[1].
So if you just need any stable Docker engine it's fine. If the latest release is required now, you're gonna run into the same issue again.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1708133

[aric49]

I think that should be added to the Docker documentation [...] Thoughts?

It is not officially supported in terms of a stable, tested release. So why should a hack like this (which is the first thing that comes to my mind to deal with the "problem" anyway) be mentioned in the official docs?
It's a calculated risk to install from the previous release's repo. It worked well in the past and so it does with F29/30 and that's probably fine for most cases. But has to be carefully considered before updating or setting up productive systems (applies to various other repos and systems as well)

I totally agree that it's a calculated risk, but I would also argue that in the absence of on-time release support, this verbiage should be added to the official docs. That being said, I believe it should also include a very plainly-stated warning that this is indeed a hack and should be taken with all caveats therein, for example that you shouldn't do this for anything critical or production-related, nor should you expect it to work 100% of the time. (And also that you are effectively going 'off book' at that point, so official support is going to be non-existent and even unofficial support will likely be thin.)

moby-engine is probably great for the vast majority of users looking to get a stable, relatively recent version of the Docker engine up and running on their fedora laptops. It seems to be like it's essentially the Fedora equivalent of docker.io package in Ubuntu. However, I'm not quite following the logic in the decision to not add a few sentences disclaimer advising Fedora users that docker-ce packages are likely releasing significantly later than the Fedora release schedule. If users want to use docker-ce, then they should install the version for the previous Fedora distro, or install the moby-engine package. I feel like it's a harmless addition to the documentation that clears up questions and gives users a work around until the distro-specific packages drop. As @rux616 mentions, plainly stating it's a work around ensures that it's not a officially supported solution by Docker. It's either that, or build packages that drop with the Fedora release schedule. This way, you won't have GitHub issues opening every time a Fedora release drops 👍

[seemethere]

Hello everyone here,

Sorry for the delayed update but the containerd.io package has been uploaded for Fedora 30 on the test channel.

If you'd like to try the upcoming release on Fedora 30 feel free to use the convenience script to install:

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

[LucasCalazans]

It worked like a charm, thanks @seemethere

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

[chrisckc]

It seems that containerd.io is now released but docker-ce and docker-ce-cli are still not:

$dnf list docker-ce
Last metadata expiration check: 0:08:46 ago on Thu 04 Jul 2019 11:19:37 BST.
Error: No matching Packages to list    

$dnf list containerd.io
Last metadata expiration check: 0:08:30 ago on Thu 04 Jul 2019 11:19:37 BST.
Available Packages
containerd.io.x86_64 

$dnf list docker-ce-cli
Error: No matching Packages to list

Used the script as suggested above instead:
curl -fsSL get.docker.com | CHANNEL=test sh

What would be the best way of updating to stable channel once it is released?

[AkihiroSuda]

Here is a workaround:

$ podman run -d --name dinp --privileged -v /run/dinp:/var/run -v /var/lib/dinp:/var/lib/docker docker:dind dockerd -H unix:///var/run/docker.sock
$ ln -s /run/dinp/docker.sock /var/run/docker.sock
$ podman exec dinp cat /usr/local/bin/docker > /usr/local/bin/docker
$ chmod +x /usr/local/bin/docker

[localleon]

It seem's like this is fixed! The Docker-CE Repository on Fedora 30 provides me with:
containerd.io.x86_64 1.2.6-3.3.fc30 @docker-ce-stable and
docker-ce.x86_64 3:18.09.5-3.fc29 @docker-ce-stable

[UnR34L]

@localleon You sure ?

I still only see containerd in stable.

https://download.docker.com/linux/fedora/30/x86_64/stable/Packages/

[djanjic]

+1

Still can’t see packages.

[stklcode]

@localleon
You obviously got a mixed setup, F30 containerd.io and F29 Docker CE

containerd.io.x86_64 1.2.6-3.3.fc30 @docker-ce-stable
docker-ce.x86_64 3:18.09.5-3.fc29 @docker-ce-stable

When installing on a blank system, complete stable stack is still not available from this repo (and btw. 18.09.7 is the latest stable, not .5)

[rickatnight11]

Fedora 30 stable packages now available:

https://download.docker.com/linux/fedora/30/x86_64/stable/Packages/

[lucassantosninb]

How to migrate test version to stable? I'm using repo.

[rickatnight11]

That depends on how you switched to the test repo, but looking at my /etc/yum.repos.d/docker-ce.repo repo config, I see there are already repos for both test and stable. Just make sure that the stable repo has enabled=1 (and test has enabled=0), and you should be set.

Ultimately this is the only config you need:

[docker-ce-stable]
name=Docker CE Stable - $basearch
baseurl=https://download.docker.com/linux/fedora/$releasever/$basearch/stable
enabled=1
gpgcheck=1
gpgkey=https://download.docker.com/linux/fedora/gpg

[kostich]

This can be closed. There are stable packages for Fedora 30 for a couple of days now and you can get the latest Docker on Fedora 30 by following the official page.