Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update KubernetesIngress docker builds #2446

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

benjaminpetit
Copy link
Member

No description provided.

@tomap
Copy link

tomap commented Mar 20, 2024

-c Release is now the default with DotNet publish in .Net 8

@benjaminpetit
Copy link
Member Author

-c Release is now the default with DotNet publish in .Net 8

Better to be explicit :)

@benjaminpetit benjaminpetit merged commit a129ed1 into dotnet:main Mar 28, 2024
7 checks passed
WORKDIR /app
EXPOSE 80
EXPOSE 443

FROM amd64/buildpack-deps:jammy-curl AS publish
FROM mcr.microsoft.com/dotnet/sdk:8.0 AS publish
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we install dotnet sdk via dotnet-install script, do we still need to use sdk image as base image?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question, we still need to install the SDK because we target versions that are not published in docker.

The SDK docker image contains dependencies needed for the dotnet script to run properly.

@MihaZupan MihaZupan added the Type: Infrastructure Infrastructure work that does not affect the actual shipping code label May 3, 2024
@MihaZupan MihaZupan modified the milestones: v.Next, YARP 2.2.0-preview1 May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Kubernetes Ingress Controller Type: Infrastructure Infrastructure work that does not affect the actual shipping code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants