unkin/jellyfin-ha
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: align runtime image .NET to the app (9.0) #7

Merged
benvin merged 1 commits from benvin/jellyfin-dotnet9 into main 2026-08-15 18:44:52 +10:00
Conversation 0 Commits 1 Files Changed 2
+7 -4
unkin-agent commented 2026-08-15 18:40:19 +10:00
Member
Copy Link
Copy Source

v0.1.2 crashes on start: the runtime image is based on mcr.microsoft.com/dotnet/aspnet:10.0 (ships .NET 10.0.11 only), but the publish step builds framework-dependent against mcr.microsoft.com/dotnet/sdk:9.0, so the server requires Microsoft.NETCore.App 9.0.0 and the host fails the framework check.

Aligns the runtime major down to the app target (upstream Jellyfin targets net8/net9; the SDK here is 9.0), rather than moving the app up to net10.

Changes:

  • Pin Dockerfile.runtime base image to mcr.microsoft.com/dotnet/aspnet:9.0 so the runtime provides .NET 9 matching the SDK 9.0 publish.
  • Add a comment tying the runtime major to the SDK major in .woodpecker/*.yaml / Makefile.
  • Fix stale ".NET 10" references in README.md.

Note: real proof is a rebuilt image starting past the .NET framework check, which happens after merge (cut v0.1.3, build+push, run-test).

v0.1.2 crashes on start: the runtime image is based on `mcr.microsoft.com/dotnet/aspnet:10.0` (ships .NET 10.0.11 only), but the publish step builds framework-dependent against `mcr.microsoft.com/dotnet/sdk:9.0`, so the server requires `Microsoft.NETCore.App` 9.0.0 and the host fails the framework check. Aligns the runtime major down to the app target (upstream Jellyfin targets net8/net9; the SDK here is 9.0), rather than moving the app up to net10. Changes: - Pin `Dockerfile.runtime` base image to `mcr.microsoft.com/dotnet/aspnet:9.0` so the runtime provides .NET 9 matching the SDK 9.0 publish. - Add a comment tying the runtime major to the SDK major in `.woodpecker/*.yaml` / `Makefile`. - Fix stale ".NET 10" references in `README.md`. Note: real proof is a rebuilt image starting past the .NET framework check, which happens after merge (cut v0.1.3, build+push, run-test).
unkin-agent added 1 commit 2026-08-15 18:40:19 +10:00
fix: align runtime image .NET to the app (9.0)
ci/woodpecker/pr/build Pipeline was successful
Details
c7409d0812 
The runtime image based on aspnet:10.0 provides only .NET 10.x, but the
publish step builds framework-dependent against SDK 9.0, so the app requires
Microsoft.NETCore.App 9.0.0 and crashes on start under 10.x.

Pin the runtime base to aspnet:9.0 to match the SDK 9.0 publish.
benvin merged commit 4a4965921f into main 2026-08-15 18:44:52 +10:00
benvin deleted branch benvin/jellyfin-dotnet9 2026-08-15 18:44:52 +10:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
benvin (BenVincent) unkin-agent (Unkin Agent) unkinben (Ben Vincent)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/jellyfin-ha#7
Delete Branch "benvin/jellyfin-dotnet9"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?