This may help (Raspberry PI 4 (linux-arm/linux-arm64)
#2180 (comment)

@michaelpeng36 Pinging to increase priority on this if possible. It is closely related to #2834 because anyone attempting to develop Functions in a VS Code devcontainer while on an M1 Mac will be blocked.

Agree 100%. I'm in the same boat. Cannot run on a Mac M1 inside a container.

@alecglen That's exactly what I'm attempted and failed to do 😆 .

Hi @michaelpeng36 any update on this?

@michaelpeng36 Pinging to increase priority on this if possible. It is closely related to #2834 because anyone attempting to develop Functions in a VS Code devcontainer while on an M1 Mac will be blocked.

Yeap, I had to reverse to an emulated container in x64 to have the func tools ... and it is very slow now :(

Hey folks, sorry for missing these pings. I am no longer the primary engineer for Core Tools, so I'm not sure when this will get fixed, but I have reached out to the new owning team to get this prioritized. @khkh-ms , would you mind taking a look?

@khkh-ms Any update on this being triaged or assigned?

I'd really like a Linux ARM64 binary for my Chromebook. There's already support for .NET SDK's and VS Code for ARM64, they are working great
I've just seen a PR for Azure CLI to support ARM64.
So it only makes sense for this to drop next, please and thank you

Update: This worked on my Chromebook with Debian bullseye Arm64 👍 It is a lengthy process to get it it built and added to PATH if you're a Linux noob like me.

This may help (Raspberry PI 4 (linux-arm/linux-arm64) #2180 (comment)

I'd really like a Linux ARM64 binary for my Chromebook. There's already support for .NET SDK's and VS Code for ARM64, they are working great I've just seen a PR for Azure CLI to support ARM64. So it only makes sense for this to drop next, please and thank you

Update: This worked on my Chromebook with Debian bullseye Arm64 👍 It is a lengthy process to get it it built and added to PATH if you're a Linux noob like me.

This may help (Raspberry PI 4 (linux-arm/linux-arm64) #2180 (comment)

azure-cli on ARM64 has been supported for a long time. But yes, it'd be awesome to have also azure-func-core-tools for aarch64

I'd really like a Linux ARM64 binary for my Chromebook. There's already support for .NET SDK's and VS Code for ARM64, they are working great I've just seen a PR for Azure CLI to support ARM64. So it only makes sense for this to drop next, please and thank you
Update: This worked on my Chromebook with Debian bullseye Arm64 👍 It is a lengthy process to get it it built and added to PATH if you're a Linux noob like me.

This may help (Raspberry PI 4 (linux-arm/linux-arm64) #2180 (comment)

azure-cli on ARM64 has been supported for a long time. But yes, it'd be awesome to have also azure-func-core-tools for aarch64

I had a look for it and tried installing azure-cli, although it pulled a package and installed something - it didn't work sadly due to python issue. Which is what this PR seems to be all about, as well as closing of a feature request from 2018 to support arm64.

+1 on an ask to include azure functions install for arm64... the new Linux VMs for Ubuntu 22.04 LTS on Ampere ARM chips is a price performance leader for servers. azure-cli works (after python fix), dotnet is supported very well, VSCode supported well... just need Azure functions!

Another voice here. Using dev containers on M1/M2 Mac fails because there's no Linux ARM support for Core Tools.
Since support was added for M1/M2 macs, aarch64 should also be supported.

It's been about 7 months since this issue was opened. Is there any movement / progress on azure function core tools adding support for aarch64?

Also running into the same issue, func fails to run inside linux devcontainers when running on M1 Macs.

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

May I know, when are you planning to release it for Linux Aarch64? It would be really helpful for us if it were available for Aarch64.

Yes why is it years before we get this basic capability, especially when the M1/M2 macs are commonly used for software development? It's not just this, MS has also not provided the capability to emulate Cosmos DB on arm64 processors, forcing developers to use cloud Cosmos for devlopment -- a very costly path. It seems MS has deprioritized Mac with Apple Silicon all around.

I've just built the binaries myself, you can try from here:
https://github.com/mohsinonxrm/azure-functions-core-tools/releases/tag/4.23_arm64

Otherwise you can build it yourself as well but dotnet release -r linux-arm64

Next, you can use the azure function dotnet docker images:
https://hub.docker.com/r/mohsinonxrm/azure-functions-dotnet/tags

@mohsinonxrm, can you point me to a repo that has the Dockerfile you used for these builds? I'd appreciate it :).

Now that #915 is closed as "support for ARM 64 is now released", may we please have an update on when Linux arm64 support will also land?

As per @lucasfijen in Azure/azure-functions-python-worker#915 (comment), azure-functions-core-tools has still not landed in the binary-arm64 Packages file, which prevents using it in arm64 devcontainers.

It's now 2024, and this issue is still open, and is causing a real headaches for our devs using Apple silicon.

@khkh-ms Can we please get an update on this?

any ETA on this ?

Same here would appreciate an ETA on this.

There's a pull request, #3584, that references this issue. It's been open for 2 months without anybody reviewing it.

I suggest we bug people on that thread as well :)

We ended up making our own image for the Dev Container and building the PR's branch instead of using the official binaries.

Seems to work fine so far.

Same here - I have to somehow get the azure-functions-core-tools working in a devcontainer on apple silicon.
I'm currently using the workaround build of @mohsinonxrm via a custom Dockerfile (see below), but it doesn't feel right.

FROM node:18-bullseye

# Install azure function core tools using the workaround
RUN curl -L https://github.com/mohsinonxrm/azure-functions-core-tools/releases/download/4.23_arm64/Azure.Functions.Cli.linux-ARM64.zip -o azure-functions-cli.zip \
    && unzip azure-functions-cli.zip -d /opt/ \
    && mv /opt/Azure.Functions.Cli.linux-ARM64 /opt/azure-functions-cli \
    && ln -s /opt/azure-functions-cli/func /usr/local/bin/func \
    && chmod +x /opt/azure-functions-cli/func \
    && rm -f azure-functions-cli.zip

We have had a little success forcing our devcontainers to be amd64

FROM --platform=linux/amd64

https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/a16c5107062573403490f01819dd5bbde1b41cb1/.devcontainer/Dockerfile#L1

We have had a little success forcing our devcontainers to be amd64

I was able to run a node project this way on an M3 mac in devcontainers.

We have had a little success forcing our devcontainers to be amd64

FROM --platform=linux/amd64

This does work somewhat, but it is SUPER SLOW. I wasn't able to install any VS Extensions for Python and Azure Functions to actually debug and work work with the code. The install would go on and on forever... (really slow)

We have had a little success forcing our devcontainers to be amd64
FROM --platform=linux/amd64

This does work somewhat, but it is SUPER SLOW. I wasn't able to install any VS Extensions for Python and Azure Functions to actually debug and work work with the code. The install would go on and on forever... (really slow)

Can confirm exactly this, PyLance hangs in while installing and it is extremely slow.

Same here - I have to somehow get the azure-functions-core-tools working in a devcontainer on apple silicon. I'm currently using the workaround build of @mohsinonxrm via a custom Dockerfile (see below), but it doesn't feel right.

FROM node:18-bullseye

# Install azure function core tools using the workaround
RUN curl -L https://github.com/mohsinonxrm/azure-functions-core-tools/releases/download/4.23_arm64/Azure.Functions.Cli.linux-ARM64.zip -o azure-functions-cli.zip \
    && unzip azure-functions-cli.zip -d /opt/ \
    && mv /opt/Azure.Functions.Cli.linux-ARM64 /opt/azure-functions-cli \
    && ln -s /opt/azure-functions-cli/func /usr/local/bin/func \
    && chmod +x /opt/azure-functions-cli/func \
    && rm -f azure-functions-cli.zip

Has anyone getting this to work? I also followed this part here: Support running on M1 Macs

then start func fails here:

ImportError: cannot import name _observability,ImportError: cannot import name _observability,ImportError: cannot import name _observability.

No resolution so far, pip install cygrpc as suggested, failed with a missing header file or so, my platform is linux/arm64, Python 3.11 on Mac M1, having a proper build for this platform would really help.

@michaelpeng36 what's the current status of this? Anyone using devcontainer on modern Macs is blocked by this.

also, it will be blocked on upcoming Snapdragon x powered PCs.
@manekinekko any update on this?

@juergstaub
Re: ImportError: cannot import name _observability. I got the same issue. Tldr; make sure you used python3.9, not python3.10, ..

The detailed error from my side shows that it happened inside this file src/python/grpcio/grpc/_cython/_cygrpc/channel.pyx.pxi which doesn't exist under the grpcio/grpc/_cython. I searched over the binary file _cython/cygrpc.cpython-310-darwin.so and it seems like the import _observability is there.

File "src/python/grpcio/grpc/_cython/_cygrpc/channel.pyx.pxi", line 15, in init grpc._cython.cygrpc
ImportError: cannot import name _observability
ERROR: unhandled error in functions worker: cannot import name _observability

Causing problems for us too. Stops one of our devs on OSX from running our container.

2 years later, still an issue.

2 years later, still an issue.

it's clear, no matter what they say at this point, it's not a priority, or heck even a want, for them.

Hi everyone, thank you so much for your feedback and patience. We are looking into this issue and will provide an update soon.

Same here - I have to somehow get the azure-functions-core-tools working in a devcontainer on apple silicon. I'm currently using the workaround build of @mohsinonxrm via a custom Dockerfile (see below), but it doesn't feel right.

FROM node:18-bullseye

# Install azure function core tools using the workaround
RUN curl -L https://github.com/mohsinonxrm/azure-functions-core-tools/releases/download/4.23_arm64/Azure.Functions.Cli.linux-ARM64.zip -o azure-functions-cli.zip \
    && unzip azure-functions-cli.zip -d /opt/ \
    && mv /opt/Azure.Functions.Cli.linux-ARM64 /opt/azure-functions-cli \
    && ln -s /opt/azure-functions-cli/func /usr/local/bin/func \
    && chmod +x /opt/azure-functions-cli/func \
    && rm -f azure-functions-cli.zip

Has anyone getting this to work? I also followed this part here: Support running on M1 Macs

then start func fails here:

ImportError: cannot import name _observability,ImportError: cannot import name _observability,ImportError: cannot import name _observability.

No resolution so far, pip install cygrpc as suggested, failed with a missing header file or so, my platform is linux/arm64, Python 3.11 on Mac M1, having a proper build for this platform would really help.

@juergstaub I got it working. You can have a look at a full example here.

However, the important parts are the following:

1. Build the azure function core tools form source by using the workaround of @amih90:

FROM mcr.microsoft.com/dotnet/sdk:8.0 as azure-functions-core-tools

# Dotnet caching - see: https://github.com/dotnet/dotnet-docker/issues/3353#issuecomment-996013919
RUN --mount=type=cache,id=nuget,target=/root/.nuget/packages \ 
    git clone https://github.com/amih90/azure-functions-core-tools.git /tmp/azure-functions-core-tools
WORKDIR /tmp/azure-functions-core-tools
# RUN git checkout amih90/linux-arm64 \
RUN git checkout b7cb908431f6aed5b509e32fc1e56a740b6eee02 \
    && dotnet publish src/Azure.Functions.Cli/Azure.Functions.Cli.csproj --runtime linux-arm64 --output /opt/azure-functions-core-tools

2. Copy the compiled func cli to the final container.
   I'm not sure, but I think it's important to use a debian/ubuntu based base image

FROM node:18-bookworm as final
[...]
RUN ln -s /opt/azure-functions-core-tools/func /usr/local/bin/func \
&& chmod +x /opt/azure-functions-core-tools/func \
&& rm -f azure-functions-cli.zip
[...]

with the new push for aarch64 on windows or WOA and with the new load of copilot pcs and zenbooks and whatnot that has windows on arm64 architecture. There is a push for more support for that WOA platform.
But that takes time, and a lot of python packages are not supported yet for WOA.

So for the time being I came to the conclusion that using WSL on my machine to be able to develop the most freely was needed sometimes, also since arm64 distros for linux have been long supported for various projects.

But the issue i am now running into is that azure-functions-core-tools doesnt seem to work on this setup?

$ sudo npm -g update azure-functions-core-tools

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

and the linux version doesnt have a arm64 option, only amd64?
so question being, any new solution to this problem? or other news?

Or is best way to build it myself like mentioned in this thread.

So its not functional on Windows arm64, neither on Linux arm64.
Any updates you could share @shreyabatra4 ?

Hi everyone, thank you so much for your feedback and patience. We are looking into this issue and will provide an update soon.

Hi all - I'm about to remove the P1 label only because we're using a different system for tracking this going forward. This does not represent a deprioritization or anything like that.

Ack on things having been quiet here - I'm flagging this internally as well. We'll get more attention on this / the linked PR.

Any news on a estimate release date for support for Linux arm64 ?

So, with Windows 11 on ARM64 with the Microsoft Surface Laptop 7th Edition/Pro - Copilot with Snapdragon Elite -- This fails when running a containerized project approach --

There is NO image for arm64 | arm/v7 for the images below, which causes Visual Studio 2022 to "fail" the build/debug indicating a "WARNING" that there is no AMD64 image --

• mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated8.0
• mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated9.0

Bad experience IMHO as a WARNING shouldn't fail the debug session -- regardless, supplying a arm/v7 image would unblock this and make the ARM64 Surface Laptops/Pro work.