The command "emcc --version" exited with code 1 #62237
Labels
arch-wasm
WebAssembly architecture
area-Build-mono
needs-further-triage
Issue has been initially triaged, but needs deeper consideration or reconsideration
Comments
|
did you make your project from scratch on .net 6 or was it ported> |
|
I ported an existing project from scratch. Anyway it works locally on my Windows 10 machine, so the project is ok. |
dotnet-issue-labeler
bot
added
area-Codegen-AOT-mono
untriaged
|
Do you have python installed? If installing that doesn't help, then you could build with I did improve this in #61067 so the error should surface better in future versions. |
radical
added
arch-wasm
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescribe the bugWe are publishing our Blazor WASM app using Docker (Linux environment) and when we choose to build it using AOT we receive the below error: To ReproducePublish Blazor WASM app using docker with This is our Dockerfile: FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
WORKDIR /src
COPY ["MyProj/MyProj.csproj", "MyProj/"]
RUN dotnet workload install wasm-tools
RUN dotnet restore "MyProj/MyProj.csproj"
COPY . .
WORKDIR "/src/MyProj"
RUN dotnet build "MyProj.csproj" -c Release -o /app/build
FROM build AS publish
RUN dotnet publish "MyProj.csproj" -c Release -o /app/publish
FROM fholzer/nginx-brotli:v1.19.1 AS final
WORKDIR /var/www/html
COPY --from=publish /app/publish/wwwroot .
COPY MyProj/nginx.conf /etc/nginx/nginx.confExceptions (if any)Blazor wasm tools installation logs: Failed publish:
|
|
This issue has been marked |
|
Hello @radical, you are right, the problem is that python3 is not installed. Thanks for #61276 because it is really needed to help developers to understand what is the problem during the build. But now I have some questions/remarks: I'm using the official Microsoft docker image for .NET6 But at this point if |
ghost
added
needs-further-triage
wasm projects with AOT, are just one kind of project that can be built with .net 6, and not everyone would need it. I'm guessing that's why they don't include it. You could file an issue in that repo, and discuss if you want to.
I'm not sure if installing it ourselves would make sense, but we should at least check that python3 is installed, when installing the workload on linux (thanks for the suggestion!). On other platforms it is included in the workload. This difference is due to how Emscripten structures it. Closing this as resolved by #61276 . |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
We are publishing our Blazor WASM app using Docker (Linux environment) and when we choose to build it using AOT we receive the below error:
To Reproduce
Publish Blazor WASM app using docker with
sdk:6.0image.This is our Dockerfile:
Exceptions (if any)
Blazor wasm tools installation logs:
Failed publish:
The text was updated successfully, but these errors were encountered: