Dmitrii Mukhin
Dmitrii Mukhin
> Yes - I too have the same issue with the following `docker-compose.yml` file: > > ``` > version: '3' > services: > db: > image: "postgres:13.4" > container_name: api-db...
> Just a quick update: > > I was able to solve this for some use cases. You need to use volumes instead of shared folders: > > e.g. for...
> export DOCKER_DEFAULT_PLATFORM=linux/amd64 I tried to do that. Didn't help. 
> I'm not familiar with how colima works, maybe that has something to do with this? Otherwise, I've seen other issues pop up with arm support that can be resolved...
Everything works as expected on last version
You can use another workaround - use 'hostname' tool. ``` environment: - DOCKER_HOST=$(hostname -f) ```
This issue presents with Cisco AnyConnect as well. When connected to SSL VPN with Cisco AnyConnect the issue is present. Containers are unreachable by domain name. Services behind SSL VPN...
I figured out that this [db-hack](https://github.com/foxcpp/go-imap-sql/blob/ee5bc28d4278a40b348b5461f203e1211147bfda/dbhacks.go#L52) doesn't work on my deployment. I didn't find how to force maddy to run that hack on init db. Also I didn't find how...
Ok. Thank you. Previous error has gone. I suppose your commit fixed that issue.