ModuleNotFoundError: No module named 'urllib3.packages.six'

By -

I'm not able to run my airflow image. It builds successfully, but when I use docker-compose up and bring up the image, it throws the following error and exits.

Unable to load the config, contains a configuration error.
Traceback (most recent call last):
  File "/usr/lib64/python3.6/logging/config.py", line 390, in resolve
    found = getattr(found, frag)
AttributeError: module 'airflow.utils.log' has no attribute 'file_task_handler'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.6/logging/config.py", line 392, in resolve
    self.importer(used)
  File "/usr/local/lib/python3.6/site-packages/airflow/utils/log/file_task_handler.py", line 24, in <module>
    import requests
  File "/usr/lib/python3.6/site-packages/requests/__init__.py", line 43, in <module>
    import urllib3
  File "/usr/lib/python3.6/site-packages/urllib3/__init__.py", line 8, in <module>
    from .connectionpool import (
  File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 11, in <module>
    from .exceptions import (
  File "/usr/lib/python3.6/site-packages/urllib3/exceptions.py", line 2, in <module>
    from .packages.six.moves.http_client import (
ModuleNotFoundError: No module named 'urllib3.packages.six'

Of course I have googled around and found nothing that fixed it. I've tried fixing any possible errors with my dockerfile, restarting docker, rebuilding the image.

Here's a portion of my dockerfile.

RUN pip3 install  pytz --cert root.pem \
    && pip3 install pyOpenSSL --cert root.pem \
    && pip3 install ndg-httpsclient --cert root.pem \
    && pip3 install pyasn1 --cert root.pem \
    && pip3 install teradatasql --cert root.pem \
    && pip3 install --trusted-host=files.pythonhosted.org  --trusted-host=pypi.org apache-airflow[crypto,celery,postgres,hive,jdbc,kubernetes,mysql,mssql,ssh,ldap]==${AIRFLOW_VERSION} --cert root.pem \
    && pip3 install 'redis==3.2' --cert root.pem \
    && pip3 install Cython --cert root.pem \
    && pip3 install xmlrunner --cert root.pem \
    && pip3 install unittest-xml-reporting --cert root.pem \
    && pip3 install pyodbc --cert root.pem \
    && pip3 install flask-bcrypt --cert root.pem \
    && pip3 install python-ldap --cert root.pem \
    && pip3 install ldap3 --cert root.pem \
    && pip3 install emoji --cert root.pem \
    && pip3 install urllib3 --cert root.pem


from Recent Questions - Stack Overflow https://ift.tt/3knxBTr
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more