This is a pretty bizarre situation I have encountered. I have the following simple Python script:
from selenium import webdriver
from selenium.webdriver.firefox.options import Options
options = Options()
options.add_argument("-headless")
browser = webdriver.Firefox(firefox_options=options)
browser.get("https://www.google.com")
print(browser.current_url)
And wrapper for the script:
#!/bin/bash
wget https://github.com/mozilla/geckodriver/releases/download/v0.19.1/geckodriver-v0.19.1-linux64.tar.gz
tar -xzvf geckodriver-v0.19.1-linux64.tar.gz
chmod 777 geckodriver
mv geckodriver /usr/bin/
firefox -v
# python3 when ubuntu
python test.py
Additionally I have two Dockerfiles:
Dockerfile A (Ubuntu; works fine):
FROM ubuntu:16.04
RUN apt-get update -y && apt-get install -y python3 \
python3-pip \
firefox \
build-essential \
wget
COPY . /app
WORKDIR /app
RUN pip3 install --upgrade pip
RUN pip3 install -r requirements.txt
ENTRYPOINT ["bash"]
CMD ["test_wrapper.sh"]
Dockerfile B (Debian; crashes):
FROM continuumio/anaconda3:5.0.1
RUN apt-get update -y && apt-get install -y iceweasel \
build-essential \
wget
COPY . /app
WORKDIR /app
RUN pip install --upgrade pip
RUN pip install -r requirements.txt
ENTRYPOINT ["bash"]
CMD ["test_wrapper.sh"]
test.py run from the image built from Dockerfile B throws the following exception:
selenium.common.exceptions.WebDriverException: Message: Process unexpectedly closed with status: 1
The geckodriver.log shows the following error:
GTK_BACKEND doesn't match available displays
Has anyone encountered this and know a workaround? It shouldn't need access to a display because it's running headless - unless selenium Firefox options are different in iceweasel than regular Firefox? I expected similar behavior, and I would much prefer to use the Anaconda image
I just tried this which I was almost certain would solve it but it did not work.
EDIT: I do not believe this is a geckodriver issue as I tried the same Dockerfile with firefox-esr instead of iceweasel. Additionally, I tried starting the container interactively and executed firefox -headless (which on ubuntu launches a headless firefox session) it gave the same exact GTK error selenium does.
