Nothing Special   »   [go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

How to solve "failed to load command: middleman" on M1? #2543 #1600

Open
BigXia opened this issue Mar 24, 2022 · 5 comments
Open

How to solve "failed to load command: middleman" on M1? #2543 #1600

BigXia opened this issue Mar 24, 2022 · 5 comments

Comments

@BigXia
Copy link
BigXia commented Mar 24, 2022

Bug Description
A clear and concise description of what the bug is and how to reproduce it.

Screenshots
If applicable, add screenshots to help explain your problem.

Follow the doc step by step, but got error after run:

[192:test] docker run --rm --name slate -v $(pwd)/build:/srv/slate/build -v $(pwd)/source:/srv/slate/source slatedocs/slate build

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
bundler: failed to load command: middleman (/usr/local/bundle/bin/middleman)
/usr/local/bundle/gems/rb-inotify-0.10.1/lib/rb-inotify/notifier.rb:69:in initialize': Function not implemented - Failed to initialize inotify (Errno::ENOSYS) from /usr/local/bundle/gems/listen-3.0.8/lib/listen/adapter/linux.rb:31:in new'
from /usr/local/bundle/gems/listen-3.0.8/lib/listen/adapter/linux.rb:31:in _configure' from /usr/local/bundle/gems/listen-3.0.8/lib/listen/adapter/base.rb:45:in block in configure'
from /usr/local/bundle/gems/listen-3.0.8/lib/listen/adapter/base.rb:40:in `each'
image
https://github.com/slatedocs/slate/wiki/Using-Slate-in-Docker
image

Browser (please complete the following information):

  • OS: MacOS 12.2
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]
  • Ruby version: ruby 2.6.8p205 (2021-07-07 revision 67951) [universal.arm64e-darwin21]
  • M1 MacBook Pro

Last upstream Slate commit (run git log --author="\(Robert Lord\)\|\(Matthew Peveler\)\|\(Mike Ralphson\)" | head -n 1):
Put the commit hash here
@mbowyer-tariffcom
Copy link

@BigXia if you build the docker image manually instead of pulling the image it will work fine:

docker build . -t slatedocs/slate

@BigXia
Copy link
Author
BigXia commented Mar 26, 2022

But i want to know how to solve this issue directly rather than using another way. Do you know how to solve directly?

because i aim to solve similiar bug from another slate project which is integrated complicately and does not work with that way.

@Mdsarwe123
Copy link

Hi 37 is how total price

@Mdsarwe123
Copy link

Hi nice to meet you how are you today and who is wait this account I'm today open right bat I have world onle moments is right how every body about is seme turi you understand turi

@arnasledev
Copy link

guys, I have M1 and I had the same issue. At first, I tried to change the docker build itself and use docker-compose instead but after many failures, I've cleaned my docker totally and tried what they say in the docs:

  1. docker pull slatedocs/slate
  2. docker build . -t slatedocs/slate
  3. docker run --rm --name slate -p 4567:4567 -v $(pwd)/source:/srv/slate/source slatedocs/slate serve

and it is just working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@BigXia @arnasledev @mbowyer-tariffcom @Mdsarwe123