Open glo45343 opened 1 year ago
Hi @glo45343, is it possible that the container you're targeting is not running? That will typically produce the error message that you received.
I am running into a similar situation where mutagen-compose up
all of a sudden stopped working across all my docker projects. That said, docker-compose up
still works. See attached for a screenshot of the terminal error and docker-compose.yml
config.
Pretty sure I updated both Ventura and Docker since the last time I ran mutagen-compose up
so wondering if that could be the issue.
Specs:
UPDATE
I was able to get my env back up and running by updating mutagen to v.0.17.0 so I am all good now. That said, I looked through the releases here on Github and didn't see anything about a breaking change or conflicts with the latest docker (if in fact that was the case).
Commands for anyone else that comes along:
brew update
brew upgrade
mutagen daemon stop
mutagen daemon start
mutagen-compose up
FWIW I love this project 🥇
Connecting to agent (POSIX)...
Error: unable to create synchronization session (code): unable to connect to beta: unable to connect to endpoint: unable to dial agent endpoint: unable to create agent command: unable to probe container: container probing failed under POSIX hypothesis (exit status 1) and Windows hypothesis (exit status 1)
Mutagen version 0.17.0 ( in windows installed virtual box, in virtual box created Ubuntu OS)