profile
viewpoint

Ask questionsIncorrect Ubuntu Bionic InRelease file

<!-- This issue tracker is for bug reports and feature requests. For questions, and getting help on using docker:

  • Docker documentation - https://docs.docker.com
  • Docker Forums - https://forums.docker.com
  • Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)
  • Post a question on StackOverflow, using the Docker tag -->
  • [x] This is a bug report
  • [ ] This is a feature request
  • [x] I searched existing issues before opening this one

<!-- DO NOT report security issues publicly! If you suspect you discovered a security issue, send your report privately to security@docker.com. -->

Expected behavior

The label is in the InRelease should be Docker CE.

Actual behavior

The label is in the InRelease is Docker EE. This problem will only affect Ubuntu Bionic for now, here is the file location: https://download.docker.com/linux/ubuntu/dists/bionic/InRelease

Steps to reproduce the behavior

<!-- Describe the exact steps to reproduce. If possible, provide a minimum reproduction example; take into account that others do not have access to your private images, source code, and environment.

REMOVE SENSITIVE DATA BEFORE POSTING (replace those parts with "REDACTED") -->

Output of docker version:

(paste your output here)

Output of docker info:

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.)

Temporary Solution

Run this command to fix this problem temporarily, after Docker fix this problem, you may need to run this command again: sudo apt-get --allow-releaseinfo-change update

Note

@ypcs 
You should note, about overriding this check with commands described above (... --allow-releaseinfo-change...): those circumvent security features of APT, that have been put in place for a reason (see eg. https://manpages.debian.org/unstable/apt/apt-secure.8.en.html#INFORMATION_CHANGES).

Yes, in this case it might be just a "false alarm" caused by configuration error in Docker repository release process, but it also could be a (semi-)successful breach and eg. watering hole attack.

Anyways, this currently blocks eg. automated system upgrades and stuff like that, so hopefully they fix it soon...
docker/for-linux

Answer questions adrienbrault

If you want to know when this is reverted without actively checking, you can run this:

until curl -s https://download.docker.com/linux/ubuntu/dists/bionic/InRelease | grep -E "^Label:" | grep 'Docker CE'; do say not working yet && sleep 5 ; done; while true; do say its working; done
useful!

Related questions

docker 18.03.1-ce network not working on Deepin 15.7 - socket permission denied hot 2
yum install docker failing hot 1
Docker-CE package is missing for Ubuntu 19.10 "Eoan" hot 1
docker build slow due to slow docker-untar (not using server capacity) hot 1
Docker-CE package is missing for Ubuntu 19.10 "Eoan" hot 1
Failed install on Ubuntu bionic 18.04 in WSL hot 1
Error response from daemon: failed to listen to abstract unix socket "/containerd-shim/moby/<uuid>/shim.sock": listen unix /containerd-shim/moby/<uuid>/shim.sock: bind: address already in use: unknown hot 1
running bash from host to container is very slow hot 1
Can't Start docker.service on Ubuntu (18.04) hot 1
Docker-CE package is missing for Ubuntu 19.10 "Eoan" hot 1
Error response from daemon: failed to listen to abstract unix socket "/containerd-shim/moby/<uuid>/shim.sock": listen unix /containerd-shim/moby/<uuid>/shim.sock: bind: address already in use: unknown hot 1
yum install docker failing hot 1
Docker-CE need updating for raspbian buster hot 1
cgroups: cannot found cgroup mount destination: unknown hot 1
Support host.docker.internal DNS name to host hot 1
Github User Rank List