Multiple exceptions when deploying localstack (S3) to Kubernetes cluster via Kubeapps #10891
Open
1 task done
Labels
area: integration/kubernetes
Run LocalStack on Kubernetes
status: backlog
Triaged but not yet being worked on
type: bug
Bug report
Is there an existing issue for this?
Current Behavior
I am attempting to provide an S3 bucket to an application, using localstack (https://github.com/localstack/localstack) Helm chart as the implementation. The application has a Helm chart that I use to configure and deploy to the cluster. I added localstack as a chart dependency.
I first tested deploying to a single-node cluster provided by my locally installed Docker Desktop. I worked through various issues until the charts deployed, and as far as I am able to tell, have successfully connected and are running without errors.
My next step was to try to deploy all of this to one of our multi-node Kubernetes clusters, in this case, using Kubeapps to manage the charts deployment. A few differences in the charts values YAML is the only (obvious) difference from the prior testing.
When I do this, localstack throws multiple exceptions, that seem to be centered around a problem with Docker. It seems odd that according to these errors, it would seem that Docker is "missing".
I have attached a sample log from the localstack pod.
Expected Behavior
I would expect that no exceptions are thrown and the two applications connect successfully.
How are you starting LocalStack?
Custom (please describe below)
Steps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)I am installing the localstack Helm chart as a dependency of the app Helm chart I am attempting to integrate with localstack. The Kubeapps application is managing the installation onto our multi-node Kubernetes cluster.
Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
Environment
Anything else?
jmg-test-localstack-77dc5f9cdb-rn6k7.log
The text was updated successfully, but these errors were encountered: