Summary
Unable to retrieve credentials for Airbyte instance on Ubuntu due to ‘No such container’ error when using abctl local credentials command.
Question
Hello everyone,
I’m trying start an airbyte instance locally on ubuntu. Everything is working except that I’m unable to get credentials.
abctl local credentials
INFO Using Kubernetes provider:
Provider: kind
Kubeconfig: /home/nihal/.airbyte/abctl/abctl.kubeconfig
Context: kind-airbyte-abctl
ERROR unable to inspect container: Error response from daemon: No such container: airbyte-abctl-control-plane
nihal@nihalga:~$
airbyte-abctl-control-plane is up and running. I’m unable to figure out why we’re getting this error. Could someone please help me out?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["airbyte-instance", "ubuntu", "abctl", "credentials", "error"]
No it’s running.
docker ps -a -f name=airbyte
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8712a8b5bd67 kindest/node:v1.29.8 “/usr/local/bin/entr…” 28 minutes ago Up 28 minutes 0.0.0.0:8000->80/tcp, 127.0.0.1:45147->6443/tcp airbyte-abctl-control-plane
and what does abctl local status say?
same error.
nihal@nihalga:~$ abctl local status
INFO Using Kubernetes provider:
Provider: kind
Kubeconfig: /home/nihal/.airbyte/abctl/abctl.kubeconfig
Context: kind-airbyte-abctl
SUCCESS Found Docker installation: version 27.2.0
SUCCESS Existing cluster ‘airbyte-abctl’ found
ERROR unable to inspect container: Error response from daemon: No such container: airbyte-abctl-control-plane.
Container is visible in docker ps and docker desktop but it’s showing this error.
which linux version are you using?
Which environment are you running on?
I was using Mac OS with zero problems. Now shifted to linux becasue I have to use work laptop. I’m using Ubuntu 24.04
I wonder if there could be anything weird with the name. What about
docker ps -f name=airbyte --format json
everything looks good
docker ps -f name=airbyte --format json
{“Command”:“"/usr/local/bin/entr…"”,“CreatedAt”:“2024-09-10 00:16:31 +0530 IST”,“ID”:“8712a8b5bd67”,“Image”:“kindest/node:v1.29.8”,“Labels”:“http://desktop.docker.io/binds/1/Target=/var/local-path-provisioner,io.x-k8s.kind.cluster=airbyte-abctl,io.x-k8s.kind.role=control-plane,desktop.docker.io/binds/1/Source=/home/nihal/.airbyte/abctl/data,desktop.docker.io/binds/1/SourceKind=hostFile|desktop.docker.io/binds/1/Target=/var/local-path-provisioner,io.x-k8s.kind.cluster=airbyte-abctl,io.x-k8s.kind.role=control-plane,desktop.docker.io/binds/1/Source=/home/nihal/.airbyte/abctl/data,desktop.docker.io/binds/1/SourceKind=hostFile”,“LocalVolumes”:“1”,“Mounts”:“/host_mnt/home…,/lib/modules,6cf08b0b7b3d07…”,“Names”:“airbyte-abctl-control-plane”,“Networks”:“kind”,“Ports”:“0.0.0.0:8000-\u003e80/tcp, 127.0.0.1:45147-\u003e6443/tcp”,“RunningFor”:“42 minutes ago”,“Size”:“0B”,“State”:“running”,“Status”:“Up 42 minutes”}
any chance you have a VM running on this machine, or any other possible docker install? What does the DOCKER_HOST env var look like (is there one)?
or perhaps we can check what docker context ls says
Sounds like your abctl container isn’t running. What does
docker ps -a -f name=airbyte
say?
should it be using the default context instead of desktop-linux?
Hey Alex, qemu is running on this machine but there is no DOCKER_HOST variable.
Docker is using the desktop-linux context. I believe that belongs to docker desktop.
<@U07JY9CKLB1> Sorry, I lost track of this thread. Are you still stuck?
It does seem possible that abctl and kind (the k8s cluster library used by abctl) are using different docker contexts. You could try running docker context use default and then try abctl local credentials again