Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't run docker-compose: inotify issue on Apple M1 laptop #65

Open
bolducp opened this issue Oct 1, 2021 · 2 comments
Open

can't run docker-compose: inotify issue on Apple M1 laptop #65

bolducp opened this issue Oct 1, 2021 · 2 comments

Comments

@bolducp
Copy link

bolducp commented Oct 1, 2021

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:

services:
  db:
    image: mysql:5.7.35
    platform: linux/amd64
  waweb:
    platform: linux/arm64/v8
    image: docker.whatsapp.biz/web:v2.35.4
    command:
      [
        "sh", "-c",
        "touch /var/log/whatsapp/web.log
        && chmod 777 /var/log/whatsapp/web.log
        && sed -i 's/  monitor_file.*/  tail -f \\/dev\\/null/g' /opt/whatsapp/bin/web_setup.sh
        && /opt/whatsapp/bin/wait_on_mysql.sh
        && /opt/whatsapp/bin/launch_within_docker.sh"
      ]

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!

@facebook-github-bot
Copy link
Contributor

Hi bolducp (https://github.com/bolducp),

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.

Thanks for your understanding!

@vuvantoan95
Copy link

I also got this error :( @bolducp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants