I'm deploying Airbyte via Helm with an external da...
# ask-ai
b
I'm deploying Airbyte via Helm with an external database (have already done this without issue in 4 other environments) and this time my
temporal
pod keeps crashing with the error
Copy code
2023-05-04T17:27:33.813Z	ERROR	Unable to create SQL database.	{"error": "pq: database \"temporal\" already exists", "logging-call-at": "handler.go:97"}
2023/05/04 17:27:33 Loading config; env=docker,zone=,configDir=config
2023/05/04 17:27:33 Loading config files=[config/docker.yaml]
Unable to load configuration: config file corrupted: yaml: line 17: found unknown escape character.
I'm deploying chart 0.45.11 / airbyte version 0.44.0
k
A message from kapa.ai
Sorry @Ben Konicek, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! 🧑‍💻 Perhaps try again in 5mins?
m
I’ve been having exactly the same issue today
b
I've exec'd into the pod and I can see there is no
config/docker.yaml
, but on another deployment that file does exist in the pod
Well I'm glad it's not just me then! It's so strange because I'm using the exact same chart and application version, and I can see that even the
airbyte/temporal-auto-setup
image's tag is the same between both installations
m
I’ve been using 0.45.8. Oddly for me, I was able to deploy service on development env, where images have already been pulled, but was not able to deploy it on freshly created infra
Hmm, everything seems to work correctly when using built-in database. What version Postgres are you using?
b
13.8, same as the other environments that worked OK
I even started a debug pod that copied the failing one, and I'm able to run
entrypoint.sh
to generate the
config/docker.yaml
that it couldn't find, so it doesn't seem like anything should have been causing that script to fail from the start