Closed JoeKaldas closed 1 month ago
Try deleting the context.
docker context ls
docker context rm name_of_context_with_wrong_ip_address
I had the same issue using an AWS instance as the builder when I had to delete and restart the instance and the IP address changed.
@dotnofoolin I've tried on both instances and both had one context of default
@JoeKaldas - the context will be on the machine you are deploying from.
To fix this, we need to add a check in the build step to confirm the context is up to date with the config.
Duplicate of https://github.com/basecamp/kamal/issues/90
I'm trying to deploy on Hetzner. My setup has 2 servers, one for app and one for postgres. They talk to each other internally. Have a network setup on Hetzner for that.
Here's a screenshot of my 2 servers.![0o3_SQJ-](https://github.com/basecamp/kamal/assets/6186940/226c43e1-42f8-40b4-a8a8-ecd341db5db1)
If I try deploying using
Using remote builder for single-arch
, I get the following error. It's trying to connect to5.75.252.76
which isn't even one of my IP addresses. I tried using10.0.0.2
in my builder host but same issue.Here's my
deploy.yml