From 68401d5bb5005ba0be330073cd3c4629f36aa725 Mon Sep 17 00:00:00 2001 From: woksin Date: Thu, 6 Aug 2026 11:57:57 +0200 Subject: [PATCH] Run on a runtime image that exists MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The first publish failed to pull mcr.microsoft.com/dotnet/aspnet:10.0-bookworm-slim: there is no Debian-slim variant for .NET 10 (those stop at 9.0), so that tag never resolved. Use 10.0-noble, which is what Studio's services run on. Verified by building the image locally and starting it: the container comes up and stops exactly where it should without configuration — the startup validation for a missing Discord token. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_015LV2femm3ZR47Lk2SscwJb --- Docker/Dockerfile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Docker/Dockerfile b/Docker/Dockerfile index 5b60909..1e983a4 100644 --- a/Docker/Dockerfile +++ b/Docker/Dockerfile @@ -18,7 +18,9 @@ RUN dotnet publish Source/Prompter.csproj --configuration ${CONFIGURATION} -p:Ve #################################### # Bot mode hosts Kestrel (health probe + re-index webhook), so the runtime needs the ASP.NET Core # shared framework. EXPOSE 8080 is Kestrel's default container port for the /healthz and /reindex routes. -FROM mcr.microsoft.com/dotnet/aspnet:10.0-bookworm-slim +# 10.0-noble is the tag Studio's services run on; the bookworm-slim variant this used to name does not +# exist for .NET 10 (Debian slim images stop at 9.0), which is why the first publish failed to pull. +FROM mcr.microsoft.com/dotnet/aspnet:10.0-noble WORKDIR /app COPY --from=build /app/publish .