Broken aspdotnet-debug docker version 3-8.0

Technical Support
,
1

I found that 3-8.0 is now referencing dotnet 6.0.33.

It appears that there must have been an update to 3-6.0 that accidentally was referenced by a lot of other versions of the aspdotnet-debug image.

2

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

:handshake:

It seems like you’re encountering an issue with the ASP.NET debug Docker image version 3-8.0, which is now referencing .NET 6.0.33. This could be due to an update that inadvertently affected multiple versions of the aspdotnet-debug image.

To address this issue, you can try the following steps:

  1. Verify the Image Version: Ensure that your project is explicitly referencing the correct version of the aspdotnet-debug image. You can do this by checking your Dockerfile or the configuration in your IDE.

  2. Update Your Dockerfile: If the image version is incorrect, update your Dockerfile to reference the desired version explicitly. For example:

    FROM mcr.microsoft.com/dotnet/aspnet:6.0.33 AS base

  3. Clear Docker Cache: Sometimes, Docker might use cached layers that could cause issues. Clear your Docker cache and rebuild the image:

    docker system prune -a
docker build --no-cache -t your-image-name .

  4. Check for Updates: Ensure that your development environment, including the Torizon extension and Docker, is up to date. This can help avoid compatibility issues.

  5. Rebuild and Redeploy: After making the necessary changes, rebuild and redeploy your application to see if the issue is resolved.

If the problem persists, it might be helpful to check the release notes or changelog for the aspdotnet-debug image to identify any recent changes that could have caused this issue.

Best regards, Toradex AI Assistant

3

Greetings @lucashutyler,

I confirmed your observation. I can see that the torizon/aspdotnet-debug:3-8.0 container image does contain .NET 6 instead of .NET 8. I will report this to our team.

One question though, how did you notice this? Are you using this container image directly yourself? Or are you using it in our VSCode extension?

Our aspdotnet template uses a different version tag (3.1.0-8.0.2): vscode-torizon-templates/aspnetBlazor/Dockerfile.debug at dev · toradex/vscode-torizon-templates · GitHub

This version does properly have .NET 8. So I’m wondering why you were using the 3-8.0 version tag instead.

Best Regards,
Jeremias

4

Hi Jeremias,

We started with a template that was on .NET 6 a while back. We have since upgraded our project to .NET 8 and browsed the torizon images on Docker Hub and found the other version.

5

I see. Well thank you for bringing this to our attention.

Best Regards,
Jeremias

6

Hi @lucashutyler,

We released a new version that fixes the issue

# docker run -it docker.io/torizon/aspdotnet-debug:3-8.0 dotnet --info 
Unable to find image 'torizon/aspdotnet-debug:3-8.0' locally
3-8.0: Pulling from torizon/aspdotnet-debug
Digest: sha256:16ad616366f36d203b6315d762abbb7214befacb397273160586cd88a7adfef3
Status: Downloaded newer image for torizon/aspdotnet-debug:3-8.0

Host:
  Version:      8.0.8
  Architecture: arm64
  Commit:       08338fcaa5
  RID:          linux-arm64

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.8 [/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.8 [/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  DOTNET_ROOT       [/dotnet]

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

We had a race condition in the container builds which resulted in the wrong image getting tagged.
As well as the fix, we’ll add a runtime test to prevent future regressions.

Apologies for the inconvenience :slight_smile:

Regards,

1 Like
7

Hi Leon,

Excellent response time for the fix for this! We appreciate the hard work.

Thank you,

Luke

1 Like