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

CRITICAL: debian's version does not match registry #65

Closed
Al2Klimov opened this issue Jan 5, 2020 · 5 comments
Closed

CRITICAL: debian's version does not match registry #65

Al2Klimov opened this issue Jan 5, 2020 · 5 comments

Comments

@Al2Klimov
Copy link

@Al2Klimov Al2Klimov commented Jan 5, 2020

... but it actually matches.

How to reproduce:

  1. Provision a new VM as show below
  2. Wait a few days so there's a new version of the Docker image debian:testing-slim
  3. In /dc
    1. docker-compose down
    2. docker pull debian:testing-slim
    3. docker-compose pull debian (just to be sure)
    4. docker-compose up -d --force-recreate
  4. Wait a few seconds
  5. check_docker --version
def mkVm (config, hostname, box, script)
  config.vm.define hostname do |cfg|
    cfg.vm.box = box
    cfg.vm.hostname = hostname

    cfg.vm.synced_folder ".", "/vagrant"
    cfg.vm.network "private_network", type: "dhcp"

    cfg.vm.provider "virtualbox" do |vb|
      vb.memory = "1024"
    end

    cfg.vm.provision "shell", inline: script
  end
end

Vagrant.configure("2") do |config|
  mkVm config, "dc", "debian/contrib-buster64", <<-SHELL
sudo bash -exo pipefail <<BASH

apt-get install -y wget python3-pip
wget -O- https://download.docker.com/linux/debian/gpg |apt-key add -

cat <<REPO >/etc/apt/sources.list.d/docker.list
deb https://download.docker.com/linux/debian buster stable
REPO

apt-get update
apt-get install -y docker-ce docker-compose

pip3 install check_docker

mkdir /dc
cd /dc

cat <<YML >docker-compose.yml
version: '2.4'
networks:
  host-debian:
    internal: true
    driver_opts:
      com.docker.network.bridge.name: docker1
    ipam:
      config:
      - subnet: 192.168.234.0/30
        gateway: 192.168.234.1
services:
  debian:
    container_name: debian
    image: debian:testing-slim
    command:
    - bash
    - -exo
    - pipefail
    - -c
    - |-
      while sleep 86400; do true; done
    restart: always
    networks:
      host-debian:
        ipv4_address: 192.168.234.2
YML

/usr/bin/docker-compose up -d --force-recreate

BASH
SHELL
end
@timdaman

This comment has been minimized.

Copy link
Owner

@timdaman timdaman commented Jan 6, 2020

Thank you for the report. The next few weeks are pretty busy for me but I am I already fixing something in the Swarm code so I will see if I can look at this at the same time.

What I am noticing is my test suites are also failing when they passed previously. I think the Docker Hub may have made a change. I did a bit digging last night and I can recreate the issue so hopefully it won't be too much work to resolve.

@timdaman

This comment has been minimized.

Copy link
Owner

@timdaman timdaman commented Jan 13, 2020

I believe version 2.2.1 should resolve this issue. Let me know if you see otherwise.

@Al2Klimov

This comment has been minimized.

Copy link
Author

@Al2Klimov Al2Klimov commented Jan 13, 2020

@timdaman

This comment has been minimized.

Copy link
Owner

@timdaman timdaman commented Jan 13, 2020

pip install check-docker==2.2.1

You can also snag the check_docker.py from the master branch which is currently sitting at 2.2.1
https://github.com/timdaman/check_docker/blob/master/check_docker/check_docker.py

@Al2Klimov

This comment has been minimized.

Copy link
Author

@Al2Klimov Al2Klimov commented Jan 13, 2020

Purrs like a cat, thanks.

@Al2Klimov Al2Klimov closed this Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.