Open keyle opened 1 year ago
I'm afraid I'm facing issues getting Colima working on my systems too - facing similar issues. If there's some guidance the community can recommend that would be ideal...
Frankly I have no way to replicate this exactly, but DNS is basically broken in Linux under Colima.
@keyle
I had exactly same issue and I can confirm that rm -f /etc/resolver/docker.amazee.io
is the only thing that worked for me.
I get following if I run pygmy status
but everything works without an issue.
@fubarhouse
I also had issues with Colima in the past on Mac M1 but after running following, all started working https://github.com/abiosoft/colima/tree/main#upgrading
colima delete # delete existing instance
colima start
That makes a bit of sense - though it doesn't help my situation.
If you could confirm this @keyle, I could perhaps write a command to write out a config value to disable the resolver.
I also forgot to mention that I always have to run pygmy up
twice after switching to Colima from Docker Desktop
First time I always get
Second time it starts without any issue.
I can confirm, I delete the resolver after every pygmy up... Otherwise it doesn't work.
@rsau you might be interested in the following solution - it is known but unrelated.
https://github.com/pygmystack/pygmy/issues/442#issuecomment-1558776329
Thanks @fubarhouse In Linux it so easy to fix that but on Mac it is another story.
Describe the bug We use the pygmy stack with amazee projects on macOS and I made the transition to Colima from Docker App (enough of that turd).
Everything appears honky dory except for the routing. Dnsmasq is not happy with
*.docker.amazee.io
. We also found a temporary fix.To Reproduce Steps to reproduce the behavior:
brew install docker docker-compose colima
docker context use colima
~/.docker/config.json
and remove line"credsStore"
if it is set to"desktop"
export DOCKER_HOST="unix://${HOME}/.colima/default/docker.sock"
to zhrc (for apps unaware of docker context)colima start --cpu 8 --memory 10 --network-address
pygmy up
docker-compose up
on an amazeeproject
Expected behavior Routing should work to
project.docker.amazee.io
Output Browser attempts to resolve the name and fails after about 30s.
ERR_NAME_NOT_RESOLVED
Additional context We have the following fix:
rm -f /etc/resolver/docker.amazee.io
following everypygmy up
. And it works without it. I am not exactly sure why it works without it, but it certainly doesn't work with it.Contents of that file:
Exported configuration