HTTP request error using docker-compose command

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu 18.04
  • Memory / Disk: 160Gb / 1 Tb
  • Deployment: Docker
  • Airbyte Version: 0.35.30-alpha
  • Source name/version:
  • Destination name/version:
  • Step: The issue is happening during docker-compose down
  • Description: I ran docker-compose down command to end airbyte but I am getting following error.
dskim@AD:~/airbyte$ docker-compose down
WARNING: The RUN_DATABASE_MIGRATION_ON_STARTUP variable is not set. Defaulting to a blank string.
WARNING: The NEW_SCHEDULER variable is not set. Defaulting to a blank string.
WARNING: The SECRET_PERSISTENCE variable is not set. Defaulting to a blank string.
WARNING: The WORKER_ENVIRONMENT variable is not set. Defaulting to a blank string.
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

I ran it again with --verbose to obtain debug information.

dskim@AD:~/airbyte$ docker-compose --verbose  down
compose.config.config.find: Using configuration files: ./docker-compose.yaml
WARNING: compose.config.environment.__getitem__: The RUN_DATABASE_MIGRATION_ON_STARTUP variable is not set. Defaulting to a blank string.
WARNING: compose.config.environment.__getitem__: The NEW_SCHEDULER variable is not set. Defaulting to a blank string.
WARNING: compose.config.environment.__getitem__: The SECRET_PERSISTENCE variable is not set. Defaulting to a blank string.
WARNING: compose.config.environment.__getitem__: The WORKER_ENVIRONMENT variable is not set. Defaulting to a blank string.
compose.cli.docker_client.get_client: docker-compose version 1.29.2, build 5becea4c
docker-py version: 5.0.0
CPython version: 3.7.10
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019
compose.cli.docker_client.get_client: Docker base_url: http+docker://localhost
compose.cli.docker_client.get_client: Docker version: Platform={'Name': 'Docker Engine - Community'}, Components=[{'Name': 'Engine', 'Version': '20.10.8', 'Details': {'ApiVersion': '1.41', 'Arch': 'amd64', 'BuildTime': '2021-07-30T19:52:16.000000000+00:00', 'Experimental': 'false', 'GitCommit': '75249d8', 'GoVersion': 'go1.16.6', 'KernelVersion': '5.4.0-94-generic', 'MinAPIVersion': '1.12', 'Os': 'linux'}}, {'Name': 'containerd', 'Version': '1.4.9', 'Details': {'GitCommit': 'e25210fe30a0a703442421b0f60afac609f950a3'}}, {'Name': 'runc', 'Version': '1.0.1', 'Details': {'GitCommit': 'v1.0.1-0-g4144b63'}}, {'Name': 'docker-init', 'Version': '0.19.0', 'Details': {'GitCommit': 'de40ad0'}}], Version=20.10.8, ApiVersion=1.41, MinAPIVersion=1.12, GitCommit=75249d8, GoVersion=go1.16.6, Os=linux, Arch=amd64, KernelVersion=5.4.0-94-generic, BuildTime=2021-07-30T19:52:16.000000000+00:00
compose.cli.verbose_proxy.proxy_callable: docker inspect_network <- ('airbyte_default')
compose.cli.verbose_proxy.proxy_callable: docker inspect_network -> {'Attachable': True,
 'ConfigFrom': {'Network': ''},
 'ConfigOnly': False,
 'Containers': {'1aa21ab12867c91509d016b15a8d2aa664fa7b2b20e89de6d3dc8a7904f229b8': {'EndpointID': '8a482c6e9f762174780ba8b9b918f588668204442429dbc330bc93301f532749',
                                                                                     'IPv4Address': '192.168.112.6/20',
                                                                                     'IPv6Address': '',
                                                                                     'MacAddress': '02:42:c0:a8:70:06',
                                                                                     'Name': 'airbyte-temporal'}},
 'Created': '2022-06-10T22:17:47.71850444+09:00',
 'Driver': 'bridge',
...
compose.cli.verbose_proxy.proxy_callable: docker inspect_volume <- ('airbyte_db')
compose.cli.verbose_proxy.proxy_callable: docker inspect_volume -> {'CreatedAt': '2022-06-11T13:45:43+09:00',
 'Driver': 'local',
 'Labels': {'com.docker.compose.project': 'airbyte',
            'com.docker.compose.version': '1.29.2',
            'com.docker.compose.volume': 'airbyte_db'},
 'Mountpoint': '/var/lib/docker/volumes/airbyte_db/_data',
 'Name': 'airbyte_db',
 'Options': None,
 'Scope': 'local'}
compose.cli.verbose_proxy.proxy_callable: docker inspect_volume <- ('airbyte_data')
compose.cli.verbose_proxy.proxy_callable: docker inspect_volume -> {'CreatedAt': '2021-08-27T10:50:51+09:00',
 'Driver': 'local',
 'Labels': {'com.docker.compose.project': 'airbyte',
            'com.docker.compose.version': '1.29.2',
            'com.docker.compose.volume': 'airbyte_data'},
 'Mountpoint': '/var/lib/docker/volumes/airbyte_data/_data',
 'Name': 'airbyte_data',
 'Options': None,
 'Scope': 'local'}
compose.cli.verbose_proxy.proxy_callable: docker inspect_volume <- ('airbyte_workspace')
compose.cli.verbose_proxy.proxy_callable: docker inspect_volume -> {'CreatedAt': '2022-06-11T09:17:58+09:00',
 'Driver': 'local',
 'Labels': {'com.docker.compose.project': 'airbyte',
            'com.docker.compose.version': '1.29.2',
            'com.docker.compose.volume': 'airbyte_workspace'},
 'Mountpoint': '/var/lib/docker/volumes/airbyte_workspace/_data',
 'Name': 'airbyte_workspace',
 'Options': None,
 'Scope': 'local'}
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=False, filters={'label': ['com.docker.compose.project=airbyte']})
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 1 items)
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('1aa21ab12867c91509d016b15a8d2aa664fa7b2b20e89de6d3dc8a7904f229b8')
ERROR: compose.cli.errors.log_timeout_error: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

I can’t kill airbyte-temporal container with docker stop or docker kill command.

Hey do you think this is related to this https://github.com/docker/compose/issues/3633?

Thank you. I solved the problem through docker-compose up after the process was forced to exit, but I didn’t find the cause.

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.