Updating Docker container time sync in Airbyte


The user is experiencing slow performance when transferring large tables from MySQL to MSSQL in Airbyte running as a Docker image. They are looking to fix a clock issue where the date/time in the logs differs from the host machine datetime. They are considering updating the compose.yaml file with volume mounts for timezone and localtime. They are seeking confirmation on whether this is the correct approach and whether these volume mounts should be added to each service with the volumes property.


I’m running Airbyte as a docker image from the git repo. It’s working for small tables and csv files. but very slow for large tables (40GB) mysql to mssql EL’s. Before I try to solve that issue, I wanted to fix a clock issue. The date/time in the logs as viewed in the web GUI is different to the host machine datetime.

Seems the solution is to update the compose.yaml file with the following:

  - "/etc/timezone:/etc/timezone:ro"
  - "/etc/localtime:/etc/localtime:ro"```

Is this the correct way?
Do I add this to each services with the volumes property?



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1713501279282029) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

["docker-container", "time-sync", "airbyte", "mysql", "mssql", "performance", "compose.yaml", "volumes", "timezone", "localtime"]