Skip to content
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.

[1LP][RFR] Update docker-py 1.10 to docker 4.2 #10082

Merged
merged 1 commit into from
May 14, 2020

Conversation

mshriver
Copy link
Member

@mshriver mshriver commented Apr 29, 2020

The structure of the library changed significantly, thus dockerbot needed significant changes

We no longer need to process info from inspect, and the interface for creating an running containers has completely changed.

I moved some of the logging around, and changed the logic to accommodate the docker API changes.

NOTE:
I stopped short of updating the dockerfile for the pytest container. It needs to be rewritten to use quickstart, but that is out of scope of trying to update our docker dependency.

The DockerInstance changes can be verified by running miq-selenium-container

@mshriver mshriver added tech-debt requirements Changes to requirements labels Apr 29, 2020
@mshriver mshriver changed the title [WIPTEST] Update docker-py 1.10 to docker 4.2 [RFR] Update docker-py 1.10 to docker 4.2 Apr 30, 2020
Copy link
Contributor

@digitronik digitronik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With first look LGTM. I will test locally.
Thanks for dropping docker-py @mshriver

Copy link
Contributor

@john-dupuy john-dupuy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was able to verify that running miq selenium-container locally worked, so LGTM. Worth noting that I had to nuke my venv even after uninstalling docker-py and installing docker.

Seemed to be related to docker/docker-py#1370

@john-dupuy john-dupuy changed the title [RFR] Update docker-py 1.10 to docker 4.2 [1LP][RFR] Update docker-py 1.10 to docker 4.2 May 6, 2020
@digitronik digitronik self-assigned this May 6, 2020
Copy link
Contributor

@digitronik digitronik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested Locally works fine for me 👍

@@ -33,7 +33,7 @@ def vnc_ready(addr, port):
@click.option('--image', help='Chooses selenium container image',
default=docker_conf.get('selff', 'cfmeqe/sel_ff_chrome'))
@click.option('--vncviewer', help='Chooses VNC viewer command',
default=docker_conf.get('vncviewer', 'vinagre'))
default=docker_conf.get('vncviewer', 'vncviewer'))
Copy link
Contributor

@digitronik digitronik May 6, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optional:
Mike one thought came in mind like better to make xdg-open as default. maybe vncviewer not installed on user system

but our most of user use vncviewer

@@ -33,7 +33,7 @@ def vnc_ready(addr, port):
@click.option('--image', help='Chooses selenium container image',
default=docker_conf.get('selff', 'cfmeqe/sel_ff_chrome'))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we start using quay.io/redhatqe/selenium-standalone?

The structure of the library changed significantly, thus dockerbot needed significant changes

Change docker API in dockerbot for container start kwargs
@mshriver mshriver force-pushed the update-docker-py branch from ec975fa to 2c31fdc Compare May 12, 2020 15:17
Copy link
Contributor

@digitronik digitronik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

I will move default image to quay.io/redhatqe/selenium-standalone.

@digitronik digitronik merged commit 65e438a into ManageIQ:master May 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants