Closed bobbyqul closed 2 years ago
Hello @bobbyqul 👋 Many thanks for getting in touch. We are aware of issues when using M1 hardware, see #174. However, we do not have such a machine available here. There are no plans to acquire one either. A pull request fixing this would be greatly appreciated.
Hi! I have the same issue.
@jakobvogel I have been using the image for a few weeks on my M1 Max.
It runs as an amd64
application which uses more battery than if it were a native image and could be ran without the instruction translation, but it has been running just fine.
Hello @wSedlacek 👋 Many thanks for your message. I am very glad to hear that the image works. 😊 Did you need to set up anything in particular, or did it run out of the box?
I have just been using this docker-compose.yml
version: '3.2'
services:
s3:
image: scireum/s3-ninja:latest
ports:
- '9444:9000'
Docker Desktop 4.2, macOS 12.0.1 I have had rosetta installed, but you might need to install it if you haven't already.
@wSedlacek Thank you very much!
@bobbyqul @crisnicogonzalez Can you please check your setup based on this information? If the image works for you afterwards, what is the crucial point we should put into the README file? Installation of Rosetta?
I will try myself once I get a hand on M1 hardware, but I currently don't have it at work and I do not intend to buy it myself – there are just more fun things to get, like another motorcycle… 😅
The new 7.2.3 version of S3Ninja is now available as Docker arm64 and amd64 image.
For migration on M1 Mac from amd64 to arm64 image, you have to delete your S3Ninja Container and the old S3Ninja image.
I tried to run the amd64 image on the M1. Docker emulates the container, but i cannot connect to s3ninja.