Run the agent image on the aspnet runtime - #568
Merged
Merged
Conversation
#567 gave the agent a Kestrel listener for attachment uploads and added a FrameworkReference to Microsoft.AspNetCore.App, but Dockerfile.agent still based its runtime stage on dotnet/runtime, which does not carry that framework. Every agent image built from main since then exits at launch: Framework: 'Microsoft.AspNetCore.App', version '10.0.0' (x64) No frameworks were found. Tests and a local `dotnet run` never see it because the SDK has every framework. Found by building the compose stack from main. The runtime stage now uses dotnet/aspnet, still pinned by digest. The pin moves the base from 10.0.3 to 10.0.12. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018SydqNVaaq48Q2fpPZWesJ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
#567 gave the agent a Kestrel listener for attachment uploads (
AttachmentUploadEndpoint) and added<FrameworkReference Include="Microsoft.AspNetCore.App" />toRockBot.Agent.csproj.deploy/Dockerfile.agentstill based its runtime stage ondotnet/runtime, which does not carry that framework, so every agent image built frommainsince #567 exits at launch:Unit tests and a local
dotnet runcan't catch this — the SDK has every framework. It surfaced when building the compose stack frommainto live-test #536. The deployed agent (0.15.0) predates #567, so nothing running is broken yet; the next agent image would be.Change
The runtime stage now uses
mcr.microsoft.com/dotnet/aspnet:10.0, still pinned by digest like the rest of this Dockerfile. The pin moves the base from 10.0.3 to 10.0.12.No other image is affected:
RockBot.Agentis the only project with the ASP.NET Core framework reference that ships on aruntimebase. The gateway, sample-http agent, Blazor, and MCP server images were already onaspnet.Verification
Rebuilt the agent through the compose stack with this Dockerfile:
Exited (150)within a second).Attachment upload endpoint listening on port 8082 (POST /attachments)user.attachment.upload.request.RockBot, scheduler starts,Application started.🤖 Generated with Claude Code
https://claude.ai/code/session_018SydqNVaaq48Q2fpPZWesJ