I’m trying to run redash with the included docker-compose following the guide on https://redash.io/help/open-source/dev-guide/docker

However the image fails to build and i get this output

Collecting ibm-db>=2.0.9 (from -r requirements_all_ds.txt (line 25))
Downloading https://files.pythonhosted.org/packages/3f/61/389c6decacfed61c2724005b8c2be61f2c699f731b53af13517e5a0e6e98/ibm_db-2.0.9.tar.gz (782kB)
    Complete output from command python setup.py egg_info:
    Detected 64-bit Python
    Downloading https://public.dhe.ibm.com/ibmdl/export/pub/software/data/db2/drivers/odbc_cli/linuxx64_odbc_cli.tar.gz
    Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-build-Q5OSWZ/ibm-db/setup.py", line 164, in <module>
        file_stream = BytesIO(request.urlopen(url).read())
    File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
        return opener.open(url, data, timeout)
    File "/usr/lib/python2.7/urllib2.py", line 435, in open
        response = meth(req, response)
    File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
        'http', request, response, code, msg, hdrs)
    File "/usr/lib/python2.7/urllib2.py", line 473, in error
        return self._call_chain(*args)
    File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
        result = func(*args)
    File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
        raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
    urllib2.HTTPError: HTTP Error 500: Internal Server Error
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-Q5OSWZ/ibm-db/
You are using pip version 8.1.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
ERROR: Service 'server' failed to build: The command '/bin/sh -c if [ "x$skip_ds_deps" = "x" ] ; then pip install -r requirements_all_ds.txt ; else echo "Skipping pip install -r requirements_all_ds.txt" ; fi' returned a non-zero code: 1

Hi! It’s issue with IBM servers, and we cannot do anything with it.

Here is related discussion - they say that we should just wait, it eventually will start working. Sorry for that.

If you don’t need IBM DB2 driver - you can comment this line as a temporary workaround.

Ah makes sense. I commented the line you mentioned and it’s working like a charm now. Thanks :slight_smile: