qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2 for M1

[marcelmatsuokaa]

Hi
I'm having the error on the deploy step on the quick-start guide:

== SAM deploy ==
qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory

I've tried multiple approaches that I found, including one of the closed issues here, but I still have some issues.
My Operating System is Mac OS X 12.5.1 with Apple M1 Pro chip.
The only solution that solves the gemu-x86_64 problem was reinstalling sam (while inside the container) with ARM's version of it.
This fix does deploy, but with an internal server error:

/usr/local/lib/ruby/3.1.0/bundler/definition.rb:507:in `materialize': Could not find mysql2-0.5.4, debug-1.7.1, bindex-0.8.1, nokogiri-1.14.0-x86_64-linux, nio4r-2.5.8, websocket-driver-0.7.5, io-console-0.6.0, racc-1.6.2, date-3.3.3 in locally installed gems (Bundler::GemNotFound) | /usr/local/lib/ruby/3.1.0/bundler/definition.rb:507:in `materialize': Could not find mysql2-0.5.4, debug-1.7.1, bindex-0.8.1, nokogiri-1.14.0-x86_64-linux, nio4r-2.5.8, websocket-driver-0.7.5, io-console-0.6.0, racc-1.6.2, date-3.3.3 in locally installed gems (Bundler::GemNotFound)

I feel that I shouldn't have touched sam or something... I read that you have tested on M1, so I might be doing something wrong, do you have any idea for this case?

[metaskills]

Thanks, I'm gonna sort this out. Working on a few issues that relate:

• Platform Support x86_64 & aarch64 crypteia#5
• Outline Arm64 Steps #143

[marcelmatsuokaa]

Hey! Just an update... I could not make it work for arm64, but with to x86_64 I had to do some small changes.
At first I've added to cookiecutter script (also i've added platform to all dockerfiles)

--platform=linux/x86_64

With this architecture I can use SAM, but it complains about docker:

Building image for "RailsLambda" requires Docker. is Docker running?

So on .devcontainer, i've added:

volumes:
      -  '/var/run/docker.sock:/var/run/docker.sock'

to the docker-compose.yml, so I can access docker inside the devcontainer.

After exposing my docker.sock to devcontainer, I got:

Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get https://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json: dial unix /var/run/docker.sock: connect: permission denied

So i've created a group and provided a read write permission to it:

# Creating a group - docker
sudo groupadd docker
# Adding user to the group "docker"
sudo usermod -aG docker $USER
sudo chmod 666 /var/run/docker.sock

After that, everything worked... I'm not sure if this changes are secure or okay to do, so I want to ask you about it. What do you think?

[metaskills]

I'm working on this under these issues. #143 Will post back when finished. Getting close.

[APysnack]

I'm also hoping for a resolution for this. Stupid M1 macs.

[metaskills]

Getting really really close.

[metaskills]

Wrapped up a bunch of work summed up here in the guides. Update to the site should happen shortly. Let me know if this helps. rails-lambda/lamby-site#60