I just installed Airbyte 0.29.17-alpha on Azure Linux VM running RHEL 8.4 using podman-compose. Pod with services started and UI works but I can not define any source or destination. I'm getting errors similar to: io.airbyte.workers.WorkerException: Error while getting spec from image airbyte/source-mssql:0.3.5. "podman images" shows that image from docker.io. Any advice?

Hi, I'm not very familiar with podman. It looks like a different flavor of docker compose? Can we see the scheduler and server logs?

Hi David, Thanks for quick response. Please find uploaded logs.

Hi @Anatoliy Zhyzhkevych there is others users facing problems deploying Airbyte on Azure. Did you try setup Airbyte using the default method in our docs? Asking because maybe the problem is not Podman.

Hi Marcos. I was following "Deploy Airbyte" docs page and ran: git clone https://github.com/airbytehq/airbyte.git cd airbyte docker-compose up but replacing to podman-compose. What is the default method?

As Davin, I'm not familiar with podman-compose and can give you a proper answer. What I can suggest is: try to run the getting start identically and ensure you can run Airbyte with your basic need. After that you can advance customizing the deployment to your favorite tool or infra needs

I have uploaded requested log files. Any clue on errors in the log related to staging area? Thanks.

@Anatoliy Zhyzhkevych did you try to use other source? Maybe the simple PokeAPI just to validate your instance can sync. This will reduce the scope of what is causing the error. Also, do you know if podman give permission to Pods to launch other Pods?

Hi Marcos. I tried PokeAPI. It works but MSSQL as source and Snowflake as destination are failing while getting specs from images.

can you delete the

airbyte/source-mssql:0.3.5

and try again? Sorry is not clear why is failing.

I take my statement back. While testing connection for PokeAPI am getting: 2021-09-17 194529 INFO () DefaultAirbyteStreamFactory(internalLog):110 - Check succeeded 2021-09-17 194531 ERROR () LineGobbler(voidCall):85 - time="2021-09-17T194531Z" level=error msg="Error waiting for container: " 2021-09-17 194531 INFO () TemporalAttemptExecution(lambda$getWorkerThread$1):168 - Completing future exceptionally... io.airbyte.workers.WorkerException: Error while getting checking connection.

Ok, is strange because you was able to setup Airbyte (getting the .env and docker-compose file from Github). Do you have access to another Cloud besides Azure?

No, our department is using only Azure and Linux VMs are RedHat RHEL 8.4. I also noticed that Snowflake source and destination only supports basic authentication. Is there a way to use key/passphrase or Okta token authenticators?

Right now we only support basic auth. We'd definitely be happy to broaden that support. If you could create an issue here with what you'd want that would be very helpful.