Unable to bash into connector images

Connector Development
1

I have a custom certificate that I want to install to access a TSL-enabled mongodb instance. After hours of analysis, I figured out the certificate needs to be installed in the connector image, in this case, airbyte/source-mongodb-v2.

I would like to bash into this image - airbyte/source-mongodb-v2:0.1.19, install the certificate, create a new image from it and make it the dev version, and see if my connection works when I run Airbyte in dev mode.

I can see the image here:

$ docker image ls | grep mongodb
airbyte/source-mongodb-v2                0.1.19          b2ca73587727   4 months ago    508MB
airbyte/source-mongodb-v2                latest          b2ca73587727   4 months ago    508MB

Simple commands such as these don’t work. What am I missing?

$ docker container run -it airbyte/source-mongodb-v2:0.1.19 bash
Unknown command: bash

$ docker container run -it airbyte/source-mongodb-v2:0.1.19 /bin/bash
Unknown command: C:/Program Files/Git/usr/bin/bash

$ docker container run -it airbyte/source-mongodb-v2:0.1.19 bin/bash
Unknown command: bin/bash

$ docker container run -it airbyte/source-mongodb-v2:0.1.19 bin/sh
Unknown command: bin/sh

Are the connectors designed such that we can’t bash into it? I have spent 2 days trying to build the whole app following instructions from here, but I have been running into one issue after another (I’ll share another thread with all the errors if all else fails). If bashing into container doesn’t work, what other options do I have to test this?

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team