You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you consider providing arm64 builds for shiny-server the same way the RStudio IDE is providing experimental builds for arm64? If they already have the workflow in place I guess it would be simple to borrow from them?
Reacted by Lluís Revilla, eitsupi, James Hill, Tomás Travis Alonso Cremnitz, Akshdeep Sandhu, Kevin Cazelles, philibe and Leonardo Schwarz
@lvalnegri Thanks but I know how to compile shiny-server for arm, I even have blog posts about it, the idea behind this request is to make the installation process easier and less time-consuming. I thought since other RStudio development team already has a workflow for compiling for arm, they could implement it as well.
I'm curious if there's been any further discussion about, or planning for, pre-built ARM64 Shiny Server binaries.
Apple silicon is popular (to say the least!) at this point and running via x86 emulation isn't the best.
Specifically, pre-built ARM64 binaries would unblock this.
@James-G-Hill AFAIK, only UTM allows to emulate x86_64 on macOS, though you're probably going to have very poor performance.
In my case, I'm running aarch64 Linux virtual machines on macOS to automate the deployment of Shiny Server in a production environment. The lack of packages makes it very difficult to mirror our x86_64 production environment.
A lot of cloud providers offer aarch64 VMs and it could be first step towards supporting them as well.
It's great to have aaarch64 builds for RStudio-Server - even if they're experimental - and I would love to see the same thing for Shiny-Server.
@James-G-Hill sorry for the super-late reply. If you haven't already figured it out, one solution is to use containers. And with containers there are effectively two steps required (assuming you want to build upon an image ... if you just want to run Shiny Server you may be able to skip to the second step, depending your needs).
Step 1: Cross-platform builds
Use the docker buildx build command with the --platform switch to build for an architecture that's (possibly) different than your builder host (e.g. your ARM64 Mac). So, for example, a possible build command might look like so:
The image produced will then run on a linux/amd64-based host, but will not run (without emulation) on, e.g., your ARM64 Mac. If your Dockerfile's base image is only available with linux/amd64, this is probably the best way to move forward (at the expense of emulation, described below). This is how I've dealt with Rocker's rocker/shiny-verse not supporting arm64 archs.
You can also create images that are multi-arch, e.g. with docker buildx build --platform linux/arm64,linux/amd64 .... Then, when you want to run that image as a container, the container runtime will typically select whichever arch matches your host's native arch. (You can override this again with something like docker run --platform linux/amd64 to run a specific arch on-demand.)
Step 2: Runtime emulation
I don't know how this is managed on other hosts and other container runtimes (e.g. containerd or podman), but they'll all be similar to how it's done with Docker and the Apple-silicon ARM64 machines: emulation. If you go into Docker settings, you'll need to enable Rosetta emulation. Via the UI it'll look like so:
With that enabled, you'll be able to run containers targeting the amd64 (or x86_64, which is an alias) platforms. Just a standard docker run ... command should work (you won't need to specify the arch, unless, as mentioned above, you really want to run a specific arch, e.g. to test emulation, which I assume is not what you're seeking to do here :-)).
All of this feels pretty clunky, though, and I still have some hope 🤞 that there'll eventually (pretty please, with sugar on top?) be official ARM64 Shiny Server binaries, since the Apple's M-series silicon is now well-established (and very performant) and AWS's Graviton silicon is increasingly forming the backbone of AWS's own internal infrastructure. In short, ARM64 isn't niche.
And shiny-server.service starts without crashes :)
(In Orbstack Linux Machine Ubuntu)
sudo systemctl status shiny-server.service
● shiny-server.service - ShinyServer
Loaded: loaded (/etc/systemd/system/shiny-server.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-01-02 22:41:39 CET; 29min ago
Invocation: a50e81aef06f4f1381c31ea7aff2942d
Main PID: 8052 (shiny-server)
Tasks: 11 (limit: 10787)
Memory: 87.4M (peak: 111.9M)
CPU: 1.739s
CGroup: /system.slice/shiny-server.service
└─8052 "[rosetta]" /opt/shiny-server/ext/node/bin/shiny-server /opt/shiny-server/ext/node/bin/shiny-server /opt/shiny-server/lib/main.js
It works from a MacOs browser via Orbstack Linux Machine Ubuntu without port forwarding, because "Allow access to container domain & IPs" is checked (by default) in Orbstack / Settings / Network
FROM --platform=${BUILDPLATFORM} ubuntu:oracular AS base
WORKDIR /
RUN apt update -y && apt-get install -y r-base r-cran-shiny gdebi-core wget
RUN wget https://download3.rstudio.org/ubuntu-18.04/x86_64/shiny-server-1.5.22.1017-amd64.deb
RUN gdebi -n shiny-server-1.5.22.1017-amd64.deb
RUN chown -R shiny.shiny /var/lib/shiny-server
EXPOSE 3838
ENTRYPOINT ["/opt/shiny-server/bin/shiny-server"]
Activity
lvalnegri commentedon Aug 22, 2022
I wrote down some notes a while back, they can still be valid https://github.com/lvalnegri/workshops-setup_cloud_analytics_machine/blob/master/raspberry-pi_jetson-nano.md
andresrcs commentedon Aug 22, 2022
@lvalnegri Thanks but I know how to compile shiny-server for arm, I even have blog posts about it, the idea behind this request is to make the installation process easier and less time-consuming. I thought since other RStudio development team already has a workflow for compiling for arm, they could implement it as well.
jcheng5 commentedon Aug 22, 2022
It's a good idea, thank you for the suggestion.
mmuurr commentedon Jan 10, 2024
I'm curious if there's been any further discussion about, or planning for, pre-built ARM64 Shiny Server binaries.
Apple silicon is popular (to say the least!) at this point and running via x86 emulation isn't the best.
Specifically, pre-built ARM64 binaries would unblock this.
James-G-Hill commentedon Apr 6, 2024
@mmuurr can you please explain / point me in the direction of the emulation you mentioned?
tw0flower commentedon Sep 16, 2024
@James-G-Hill AFAIK, only UTM allows to emulate x86_64 on macOS, though you're probably going to have very poor performance.
In my case, I'm running aarch64 Linux virtual machines on macOS to automate the deployment of Shiny Server in a production environment. The lack of packages makes it very difficult to mirror our x86_64 production environment.
A lot of cloud providers offer aarch64 VMs and it could be first step towards supporting them as well.
It's great to have aaarch64 builds for RStudio-Server - even if they're experimental - and I would love to see the same thing for Shiny-Server.
mmuurr commentedon Nov 10, 2024
@James-G-Hill sorry for the super-late reply. If you haven't already figured it out, one solution is to use containers. And with containers there are effectively two steps required (assuming you want to build upon an image ... if you just want to run Shiny Server you may be able to skip to the second step, depending your needs).
Step 1: Cross-platform builds
Use the docker
buildx buildcommand with the--platformswitch to build for an architecture that's (possibly) different than your builder host (e.g. your ARM64 Mac). So, for example, a possible build command might look like so:The image produced will then run on a
linux/amd64-based host, but will not run (without emulation) on, e.g., your ARM64 Mac. If your Dockerfile's base image is only available withlinux/amd64, this is probably the best way to move forward (at the expense of emulation, described below). This is how I've dealt with Rocker'srocker/shiny-versenot supportingarm64archs.You can also create images that are multi-arch, e.g. with
docker buildx build --platform linux/arm64,linux/amd64 .... Then, when you want to run that image as a container, the container runtime will typically select whichever arch matches your host's native arch. (You can override this again with something likedocker run --platform linux/amd64to run a specific arch on-demand.)Step 2: Runtime emulation
I don't know how this is managed on other hosts and other container runtimes (e.g. containerd or podman), but they'll all be similar to how it's done with Docker and the Apple-silicon ARM64 machines: emulation. If you go into Docker settings, you'll need to enable Rosetta emulation. Via the UI it'll look like so:

With that enabled, you'll be able to run containers targeting the
amd64(orx86_64, which is an alias) platforms. Just a standarddocker run ...command should work (you won't need to specify the arch, unless, as mentioned above, you really want to run a specific arch, e.g. to test emulation, which I assume is not what you're seeking to do here :-)).All of this feels pretty clunky, though, and I still have some hope 🤞 that there'll eventually (pretty please, with sugar on top?) be official ARM64 Shiny Server binaries, since the Apple's M-series silicon is now well-established (and very performant) and AWS's Graviton silicon is increasingly forming the backbone of AWS's own internal infrastructure. In short, ARM64 isn't niche.
philibe commentedon Jan 2, 2025
Post with similar direction with the @mmuurr post but on Orbstack and with standard amd64 binaries deb package from https://download3.rstudio.org/ubuntu-18.04/x86_64/shiny-server-1.5.22.1017-amd64.deb
I've tried shiny-server on Apple M3 Pro MacOs 15.2 Orbstack 1.9.2.
In Orbstack Linux Machine Ubuntu:
But I get
error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directoryexec /opt/shiny-server/bin/shiny-serverdoesn't crash anymore after installingg++-multilib(In Orbstack Linux Machine Ubuntu)And shiny-server.service starts without crashes :)
(In Orbstack Linux Machine Ubuntu)
It works from a MacOs browser via Orbstack Linux Machine Ubuntu without port forwarding, because "Allow access to container domain & IPs" is checked (by default) in Orbstack / Settings / Network
(I don't know if it works on native Ubuntu arm64.)
Note also, not tried yet, the NEWS of release v1.5.23.1030 Sep 30, 2024
from https://github.com/rstudio/shiny-server/blob/v1.5.23.1030/NEWS
philibe commentedon Jan 31, 2025
Ubuntu amd64 on arm 64 is emulated since Jan 14th 2025 on the Docker of Orbstack 1.9.4:
Install Rosetta on MacOs.
softwareupdate --install-rosettaDockerfile:Docker Build:
docker build --build-arg BUILDPLATFORM=linux/amd64 -t shiny-server:latest -f Dockerfile .Docker Run. (with 3839 on my example):
docker run -p 3839:3838 --platform linux/amd64 --user shiny shiny-serverAnd here we are on a browser (with 3839):
Édit:
install.packages("shiny")works also inside this x86 docker in the same arm64 MacBook.philibe commentedon Feb 26, 2026
Mac Rumors: Apple to Phase Out Rosetta 2 Starting With macOS 28 as Intel Era Ends
Tuesday June 10, 2025 7:41 am PDT by Joe Rossignol