You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm no longer able to run the docker-compose file because qemu for amd64 on docker for m1 doesn’t seem to support inotify (also described here). In the meantime, I've managed a work-around that is allowing me to run the local wabiz infrastructure by changing the docker-compose file as follows:
This essentially changes the infinite loop in the web_setup.sh script that uses inotify to check the value of whoami with a no-op. I don't think this should ever be an issue for me locally, so I feel okay about this work-around for now, but it would be really nice if the docker-compose script here could be instead updated to work with m1 laptops. Also, if you think this work-around is problematic for some other reason, that would be helpful to know. Thanks!
The text was updated successfully, but these errors were encountered:
Thank you for your comment. This GitHub repo is not actively monitored. If you need help, please check previously asked questions in the WA Business API Developer Community, or raise a Direct support ticket. Meanwhile, we are happy to continue with less time-sensitive discussions in GitHub.
I'm no longer able to run the docker-compose file because qemu for amd64 on docker for m1 doesn’t seem to support inotify (also described here). In the meantime, I've managed a work-around that is allowing me to run the local wabiz infrastructure by changing the docker-compose file as follows:
This essentially changes the infinite loop in the web_setup.sh script that uses inotify to check the value of
whoami
with a no-op. I don't think this should ever be an issue for me locally, so I feel okay about this work-around for now, but it would be really nice if the docker-compose script here could be instead updated to work with m1 laptops. Also, if you think this work-around is problematic for some other reason, that would be helpful to know. Thanks!The text was updated successfully, but these errors were encountered: