* Target net6.0
* Use new Enum.TryParse(ReadOnlySpan<char>) overload
* Replace RNGCryptoServiceProvider with RandomNumberGenerator
* ci - target net6.0 (#6594)
* Update deployment for dotnet6
* Use generic 6.0.x preview for CI
* Update direct dotnet download links
Co-authored-by: Bond_009 <bond.009@outlook.com>
- The substring `-buster-slim` isn't useful/correct.
- .NET 6 (from my team) is based exclusively on bullseye.
- If you update just `DOTNET_VERSION` to `6.0`, `docker build` will fail.
- If the goal is to force using `buster` throughout the Dockerfile, then making `DOTNET_VERSION` configurable isn't correct.
- Context: https://github.com/dotnet/dotnet-docker/blob/main/src/runtime-deps/6.0/bullseye-slim/amd64/Dockerfile#L1
Just saw this as a drive by look at your code. Is intended as helpful context.
Step 5/23 : FROM mcr.microsoft.com/dotnet/sdk:${DOTNET_VERSION}-buster as builder
manifest for mcr.microsoft.com/dotnet/sdk:5.0-buster not found: manifest unknown: manifest tagged by "5.0-buster" is not found
arm not tested
debian-stretch packages were missing for libva-drm2 so would not build
the base image mcr.microsoft.com/dotnet/core/sdk:${DOTNET_VERSION} is incorrectly referencing .NET Core 3-preview6 which will cause issues at runtime with library references being mismatched
This causes the jellyfin process to be pid 1 in the container. It can
receive signals like SIGTERM (from "docker stop", for example) and shut
down properly.
The self contained packages already contains the dotnet runtime
No need to use the dotnet runtime base image.
This should decrease the size of the image.
The common.build.sh script was removed in #1793 but the Dockerfiles
still used this to perform the dotnet publish. Remove that call and do
the publish explicitly.
Cody Robibero
Fernando Fernández
Mayur Panchal
Rich Lander
Bill Thornton
Nyanmisaka
artiume
Erik Rigtorp
ox0spy
dkanada
Mark Monteiro
Andrew Rabert
Matt
Narfinger
Bond_009
Joshua M. Boniface
Steve Hayles
Justin Fenn
Andrew Rabert
Erwin de Haan
nevado