Hello Team, I am trying airbyte for first time and...
# ask-community-for-troubleshooting
s
Hello Team, I am trying airbyte for first time and hence asking it here -> Not able to create source / destination in docker + mac silicon chip Environment • Airbyte version: 0.36.1-alpha • OS Version / Instance: mac 12.3.1 (Silicon chip) • Deployment: Docker • Source Connector and version: PokeAPI • Destination Connector and version: LocalCSV • Severity: High • Step where error happened: Deploy Current Behavior Tell us what happens. I am trying airbyte for first time in my local machine with docker, and trying to setup a sample source and destination. But when I create it, its been running for more than 30 mins and source and destination are not getting created. It just says
Please wait a little bit more…
Could this error cause an issue
airbyte-worker      | 2022-04-21 07:54:06 ERROR i.a.c.i.LineGobbler(voidCall):82 - WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
d
I am having a very similar problem. My config is basically the same of yours... But in my case I try to recreate a connection on Docker Version that works fine on the Cloud Airbyte. But it gives
"The connection tests failed. Check Connection Failed!"
And when I check the Docker logs I have a thousand of java errors... :
Caused by: io.temporal.failure.ApplicationFailure: message='error=0, Failed to exec spawn helper: pid: 149, exit value: 1', type='<http://java.io|java.io>.IOException', nonRetryable=false
*airbyte-worker   |* 	at java.base/java.lang.ProcessImpl.forkAndExec(Native Method:0) ~[?:?]
*airbyte-worker   |* 	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:314) ~[?:?]
*airbyte-worker   |* 	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244) ~[?:?]
*airbyte-worker   |* 	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110) ~[?:?]
*airbyte-worker   |* 	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073) ~[?:?]
*airbyte-worker   |* 	at io.airbyte.workers.process.DockerProcessFactory.checkImageExists(DockerProcessFactory.java:174) ~[io.airbyte-airbyte-workers-0.36.1-alpha.jar:?]
*airbyte-worker   |* 	at io.airbyte.workers.process.DockerProcessFactory.create(DockerProcessFactory.java:94) ~[io.airbyte-airbyte-workers-0.36.1-alpha.jar:?]
*airbyte-worker   |* 	at io.airbyte.workers.process.AirbyteIntegrationLauncher.check(AirbyteIntegrationLauncher.java:58) ~[io.airbyte-airbyte-workers-0.36.1-alpha.jar:?]
*airbyte-worker   |* 	at io.airbyte.workers.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:53) ~[io.airbyte-airbyte-workers-0.36.1-alpha.jar:?]
*airbyte-worker   |* 	at io.airbyte.workers.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:27) ~[io.airbyte-airbyte-workers-0.36.1-alpha.jar:?]
*airbyte-worker   |* 	at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$2(TemporalAttemptExecution.java:155) ~[io.airbyte-airbyte-workers-0.36.1-alpha.jar:?]
*airbyte-worker   |* 	at java.base/java.lang.Thread.run(Thread.java:833) ~[?:?]
s
I saw some of the threads on GIT and forum, I think airbyte is still not compatible with silicon chip. Also
platform
support is not there, hence causing the issue
d
Yes! I am getting at the same conclusion
I am trying to dig into this M1 thing to see if I understand better the issue
👍 1
s
Do let me know if you find any solution. Thanks in advance 🙂