Comments (2)
Hello! The tl;dr is that console apps will need to add a property to their project files:
<PropertyGroup>
...
<EnableSdkContainerSupport>true</EnableSdkContainerSupport>
...
</PropertyGroup>
The slightly longer form is that the container publishing target needs to be available but not necessarily enabled for all project types in order to support calling dotnet publish /t:PublishContainer
at a solution level and having all relevant projects containerize themselves. Web Projects and Worker Projects have a hook to automatically set this property, but console apps don't (because otherwise all library/etc. projects would have the ability to containerize, which doesn't make sense). So there's a bit more of a 'process' to enabling console apps. We hope to find a good way to default this property to true
for them in a later release.
from sdk-container-builds.
Aha! Thanks a lot! Just to confirm, this fixes things.
Also wanted to add that we are super happy publishing containers this way, it has cleaned up both CI and local development a lot since .NET 7. This minor hiccup does not change that.
from sdk-container-builds.
Related Issues (20)
- Unable to publish console app as container HOT 1
- warning NETSDK1198: A publish profile with the name 'DefaultContainer' was not found in the project HOT 4
- Pushing to ACR (Azure Container Registry)
- Container inferencing for AOT can move to stable repo HOT 4
- `<ContainerFamily>alpine-extra</ContainerFamily>` must be set when `<InvariantGlobalization>false</InvariantGlobalization>` HOT 9
- Determine inferencing for new Ubuntu `noble` images HOT 2
- PublishContainer Appends "dotnet <Target>.dll" to ENTRYPOINT for NativeAOT Builds HOT 11
- Output the newly-created images' full name from PublishContainer
- Add support for OCI Image Index v1 HOT 5
- Missing debug profile (compability) with worker projects HOT 4
- EnableSdkContainerDebugging causes build failure if ContainerImageTags is set
- Unable to use the ContainerRegistry as parameter on dotnet publish HOT 8
- Build fails when using ContainerBaseImage hosted within Quay with Ceph storage backplane HOT 3
- Container Publish: OCI base image without optional root mediaType fails HOT 6
- Provide a warning when a base image is unsupported
- Add an example Dockerfile to illustrate what the SDK tools do
- Document support for insecure registries HOT 5
- ContainerRepository value with a 'folder' that ends in a `'` doesn't give a good error HOT 2
- Support insecure registries with untrusted HTTPS certificates
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sdk-container-builds.