with own base image api is not starting anymore

[LennartKleymann]

If i publish using this command: dotnet publish -c Release -p:ContainerBaseImage=registry-1.docker.io/kleymannl/dotnet-libfontconfig1:latest -p:ContainerImageName=replaced/replaced -p:RuntimeIdentifier=linux-x64

the container is not starting anymore and I get following error message: replaced.path: no such file or directory

My base image looks like this:

FROM mcr.microsoft.com/dotnet/runtime-deps:7.0
RUN apt-get update
RUN apt-get install -y libfontconfig1

[baronfel]

@LennartKleymann can you provide some more information, like an https://aka.ms/binlog of the publish step?

[LennartKleymann]

BinLog is a little bit complicated, because it contains sensitive data for me. Can I share it to you privately? @baronfel

[baronfel]

Sure! Create a new developer community ticket here, and once you've created the ticket you can upload the binlog privately to that site. Then you can comment back here with the link to the ticket you just created and I'll be able to securely access the binlog.

[LennartKleymann]

Okay thanks. I attached the binlog to a private comment for microsoft only. https://developercommunity.visualstudio.com/t/sdk-container-builds:-with-own-base-imag/10461318

[baronfel]

Hi @LennartKleymann - I took a look at your binlog (thank you!) and what I found is that your base image is for a different architecture than your packaged application:

• the base image is targeted to arm64 in Docker terms
• the application is targeting linux-x64 in .NET terms, which is amd64 in Docker terms

as a result, the binaries built from your publish command are incompatible with your base image. You have two solutions here:

• change the architecture of your base image to support linux-x64 applications:
  • either only build an amd64 version of your base image, or
  • create a docker manifest version of your base image - i.e. an image that points to different architecture-specific images. This is what the .NET images do.
• publish your application for linux-arm64 - the SDK Container tooling supports this by adhering to the -r runtime selection CLI option

Separately, I'm going to log an issue against our tooling - when the base image is a single image (not a manifest list) we currently assume that the architectures match. We should actually verify this and error out, since the application will not be able to run in this scenario.

[baronfel]

@LennartKleymann can you take a look at this comment? This is what I'm hoping to get into .NET 8 that would identify and force you to handle this error case.

[LennartKleymann]

@baronfel Hey, sorry for the late response. With building my base image on the correct plattform my publsih of my API works.

I think that the comment you link is really good to prevent confusion, thank you really much.