Rosetta Linux

0 views
Skip to first unread message

Colby DuLin

unread,
Aug 4, 2024, 8:09:56 PM8/4/24
to agputtiemul
Thisquestion does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.

Now, I just need to run a binary( amd64 only ) on this VM. With UTM and Parallels, it works great as they allow you to mount Rosetta on your linux VM, but I cannot find this basic feature on VMware Fusion. Can it be that they don't support it ??


For any academic or commercial use, you need to request a license. Obtaining a license is free for academic users. After you obtained the license, you can download Rosetta. Make sure you download the version corresponding to the license you have. When you click, you can see the latest numbered release as well as several weekly releases. Numbered releases (since Rosetta3.6) are simply weekly releases that have been specially labeled - all weekly releases pass the same suite of tests that the numbered releases do.


For many version, we offer both a source and a binary version. The binary version may allow you to skip the compilation stage, but are more limited in the platforms on which they work. The "source" distribution should be useful on all platforms on which Rosetta can run. (If you're interested in noncanonical amino acids, download the NCAA rotamer libraries as well.)


To compile Rosetta you need a C++ compiler. Rosetta developers typically use GCC or Clang, although other standard-compliant compilers can be used. (See Install a complier for more information on installing a compiler.)


NOTE when you build with different extras, the extension will change. For example if you use extras=mpi, you use rosetta_scripts.mpi.linuxgccrelease instead of rosetta_scripts.default.linuxgccrelease


If you are interested in working with Rosetta code, you can build Rosetta using the Rosetta Xcode project. You can use it to build, run, debug, browse, and edit the source code. You can find the instructions on how to use Xcode to build Rosetta here.


PyRosetta is an interactive Python-based interface to Rosetta, allowing users to create custom molecular modeling algorithms with Rosetta sampling and scoring functions using Python scripting. PyRosetta was written for Python 2.6. You can follow instructions to download and install PyRosetta here and here.


For Linux, you will want to install the compiler package from your package management system. For Ubuntu and similar systems, the package "build-essential" can be installed with a command like sudo apt-get install build-essential.


Being an Apple customer, I am wondering if use a Mac Mini M1, do ALL Docker images run as expected? Does this happen via the Rosetta 2 framework? Or some other abstraction layer? What, if anything, needs to change? Can you dual-run the Intel and M1 versions of Docker Desktop on the same unit?


You can run ARM or Intel Docker containers on the Apple M1 Mac with Docker Desktop for Mac M1. I do it all the time. The default, of course, is to run the ARM version but if you use the --platform linux/amd64 parameter Docker will run the Intel version for you.


Hey there! This helped me tremendously, I am developing on my M1 Max MacBook however I ran into an issue when executing. I have a Python docker container running x86_64 (I needed this to be able to use a library that requires the x86_64 architecture) and my code is working. However I ran into issues as i executed my script stating MemoryError this prompted me to leun lscpu within my container when I found that my CPU architecture was set as x86_64 but my CPU op-mode was only 32-bit, for some reason on some level I am only running as 32-bit which restricts the amount of RAM my container can consume I believe


The demos, tutorials, protocol captures, and all example inputs are provided with the full Rosetta distribution, under the demos/ directory. Rosetta is available for license (which is free of charge to academic users) at


For RosettaCommons users, the demos repository should be automatically downloaded by the get_rosetta.sh download script. Alternatively, RosettaCommons users can download the demos repository from GitHub. e.g.


These are introductory tutorials intended as a gentle introduction to Rosetta concepts, and using common functionality of Rosetta. For additional examples and information on using Rosetta, see the demos (below) or the Rosetta documentation


Many papers using Rosetta are accompanied by a protocol capture - an example of how to use the protocol discussed in the paper. The protocol captures below aren't meant to show the best way to solve problems in the current version of Rosetta, instead they are meant to show published solutions to problems that were addressed by members of the Rosetta community. The purpose of these protocol captures is both to serve as a historical record and to assist those trying to reproduce past results. See the demos (above) for updated versions of most protocol captures.


This warning message indicates that there is a platform mismatch between the requested Docker image and the host platform. The requested image was likely built for the Linux/amd64 platform, but the host platform where the Docker image is being executed is Linux/arm64/v8.


This can cause compatibility issues and may result in errors or unexpected behavior. To resolve this issue, you may need to obtain a version of the image that is compatible with the host platform, or update the host platform to match the platform for which the image was built. But before that, let us understand the problem statement more deeply.


Rosetta 2 is a dynamic binary translator designed by Apple for use on Mac computers with Apple Silicon processors. It allows these computers to run software that was originally designed for Macs with Intel processors, which used a different instruction set architecture (ISA) called x86.


Rosetta 2 works by translating x86 instructions into ARM instructions, which are the ISA used by Apple Silicon processors. This translation happens in real-time as the software is running, which means that most applications can be used without any noticeable performance penalty.


Rosetta 2 is included with macOS Big Sur, which was released in November 2020. It runs automatically when you try to open an app that was built for x86 processors, and it usually works seamlessly in the background without any user intervention.


In addition to allowing Macs with Apple Silicon processors to run x86 applications, Rosetta 2 also includes some optimizations that can improve performance for certain types of software. For example, Rosetta 2 can use the neural engine in Apple Silicon processors to accelerate machine learning workloads.


Rosetta 2 is an important tool that allows Mac users to continue using their favorite software while transitioning to a new hardware platform. It demonstrates Apple's commitment to providing a smooth and seamless user experience, even during major platform transitions.


Rosetta is for AMD64 binaries of Docker itself, QEMU is for running the containers. New Beta feature for MacOS 13, Rosetta for Linux, has been added for faster emulation of Intel-based images on Apple Silicon.


In this example, we have a single service called web that uses the nginx:latest image, which is built for the linux/amd64 platform. We've also specified that the service should be accessible on port 8080 on the host machine, which is mapped to port 80 inside the container.


Seeing this very issue when attempting to build using --platform linux/amd64 on our Mac M1 machines with the pdfnetpython3 dependency in a Python project. The Docker build itself takes almost 10x time to build and is painfully slow to work if the build succeeds. Removing the pdfnetpython3 dependency allows us to remove the AMD64 requirement and the Docker builds do not run into the same issues.


I have used Xcode to debug rosetta projects in the past. It requires a little setup, but it works pretty well. Your system resources are identical to the MacBook Pro that I have used in the past, so it should work. What version of Xcode are you trying to use and how did you set up the executable to debug?


I am brand new to rosetta. Just found out that just to run an FlexPepDocking example is a very tedious trial-and-error procedure. Would be better if there are ways to help improve the code commenting and updating.


I had some binfmt service error message at the beginning of the install, but the installation continued, and, after a few questions, downloaded 930M for the rootfs. The version installed was the 2203. Despite the error messages (in red), everything installed smoothly and worked fine.


Here the first 3 benchs are CPU only, and show the effeciency of the translated code. The last two benchs on the other hand are GPU limited, were in those case an emulated speed of 100% of the native speed can be achieved.


After receiving my new arm board, was thinking if only we had the same rosetta 2 like tool for emulating x86 on any arm device.

And by chance, short after, landed on that page.

Nice work! So it seems you manage to do what Apple did to make x86 apps work on M1?

Are you still loking to improve perfs and compatibility so we could expect (as for Rosetta 2) to run our steam games from an arm board?


Thanks for explaining, the Mali blob is providing GLES driver (so mobile graphics) and your lib GL4ES is making the bridge to OpenGL (so that desktop graphics can be used on mobile GPU) . Clearer for me now ?


All, I wanted to give an update on this. We have finished scoping out the work required and will soon be scheduling the work. I can't give a firm date on when this will be available yet, but will update when the work is nearing completion.


_Control_Documentation/Technical_support_bulletins/Rosetta_2_required_for_ConnectWise_Control_on_the_Apple_M1_chip is 4 months old, and the announcement is heading for close to a year. Can we at least get an ETA? I do not use Rosetta so screensharing is left using other tools for me at this point.

3a8082e126
Reply all
Reply to author
Forward
0 new messages