Add a new deployment option for .Net Aspire

[hades200082]

.Net Aspire is a new development model Microsoft is pushing for .Net 8+ (which can run on Linux) that allows the project to manage the orchestration of services automatically. Read more

Another project called "Aspirate" is available that can take a .Net Aspire project and generate docker compose or kubernettes manifests from it. Read more

Together these could be used in a new build pack to build/publish .net Aspire application stacks along with spinning up containers for all required services. Aspire takes care of passing the connection strings and other details through to the various applications.

Supporting this would allow Coolify to get ahead of the game on containerised hosting and orchestration.

[coen22]

I tried it using aspirate, which can create a docker-compose file
https://github.com/coen22/AspireDockerComposeSample

The only thing that I get stuck on is that locally I run 'aspirate build' to push the images to Docker Desktop. This does not happen automatically in coolify as the generated docker compose is aimed at pushed images, instead of referencing Docker files.

I think Aspire is really cool, it works well on Azure, but none of this (docker stuff) is really supported and I ended up doing a lot of things manually which defeats the purpose.

This could be adapted though https://github.com/prom3theu5/aspirational-manifests to generate docker compose files suitable to coolify :)

[emimontesdeoca]

I did take a look at your source code as I tried basically the same, create a solution with .NET Aspire and somehow generate a docker-file.yml, then referencing it in a project in Coolify but had no look, I have problems with ports and stuff. Specially when using containers like Keycloak, or even normal APIs.

Did you manage to make it work?

I did try with your repo (https://github.com/coen22/AspireDockerComposeSample.git) and I get that error too, maybe I'm not doing it correctly?

I think supporting this in Coolify would be a gamechanger for people that skips cloud.

2024-Nov-19 11:36:56.592080
#36 exporting layers 0.0s done
2024-Nov-19 11:36:56.645018
#36 writing image sha256:8b1088a3d0285c5a984850e77479ca5279aee74fe01621ad80bf1468b01fd44c done
2024-Nov-19 11:36:56.645018
#36 naming to docker.io/library/xcw0ow8sskoskogggg8k8c0k-weatherapi done
2024-Nov-19 11:36:56.645018
#36 DONE 0.1s
2024-Nov-19 11:36:56.645018
2024-Nov-19 11:36:56.645018
#37 [weatherapi] resolving provenance for metadata file
2024-Nov-19 11:36:56.645018
#37 DONE 0.0s
2024-Nov-19 11:36:56.659063
Removing old containers.
2024-Nov-19 11:36:56.805512
Starting new application.
2024-Nov-19 11:36:57.605568
docker exec f4oo4000sc8808o88wggo8ck bash -c 'SOURCE_COMMIT=d9b3c1c9d5dae5f50bbb2dd44d8bcef61c067cc9 COOLIFY_BRANCH=main  docker compose --env-file /artifacts/f4oo4000sc8808o88wggo8ck/.env --project-name xcw0ow8sskoskogggg8k8c0k --project-directory /artifacts/f4oo4000sc8808o88wggo8ck -f /artifacts/f4oo4000sc8808o88wggo8ck/docker-compose.yaml up -d'
2024-Nov-19 11:36:57.605568
Container weatherapi-xcw0ow8sskoskogggg8k8c0k-113621252084  Creating
2024-Nov-19 11:36:57.605568
 Container react-xcw0ow8sskoskogggg8k8c0k-113621254093  Creating
2024-Nov-19 11:36:57.649445
Container react-xcw0ow8sskoskogggg8k8c0k-113621254093  Created
2024-Nov-19 11:36:57.649445
 Container weatherapi-xcw0ow8sskoskogggg8k8c0k-113621252084  Created
2024-Nov-19 11:36:57.655393
Container weatherapi-xcw0ow8sskoskogggg8k8c0k-113621252084  Starting
2024-Nov-19 11:36:57.655393
 Container react-xcw0ow8sskoskogggg8k8c0k-113621254093  Starting
2024-Nov-19 11:36:57.917643
Container react-xcw0ow8sskoskogggg8k8c0k-113621254093  Started
2024-Nov-19 11:36:57.922522
Error response from daemon: driver failed programming external connectivity on endpoint weatherapi-xcw0ow8sskoskogggg8k8c0k-113621252084 (58c0d5378b42a9e3ad1bc7b85a3a94315865b31ee9f5ab3411667f612a4dc331): Bind for 0.0.0.0:10001 failed: port is already allocated
2024-Nov-19 11:36:57.989723
Oops something is not okay, are you okay? 😢
2024-Nov-19 11:36:57.995506
Container weatherapi-xcw0ow8sskoskogggg8k8c0k-113621252084  Creating
2024-Nov-19 11:36:57.995506
 Container react-xcw0ow8sskoskogggg8k8c0k-113621254093  Creating
2024-Nov-19 11:36:57.995506
 Container react-xcw0ow8sskoskogggg8k8c0k-113621254093  Created
2024-Nov-19 11:36:57.995506
 Container weatherapi-xcw0ow8sskoskogggg8k8c0k-113621252084  Created
2024-Nov-19 11:36:57.995506
 Container weatherapi-xcw0ow8sskoskogggg8k8c0k-113621252084  Starting
2024-Nov-19 11:36:57.995506
 Container react-xcw0ow8sskoskogggg8k8c0k-113621254093  Starting
2024-Nov-19 11:36:57.995506
 Container react-xcw0ow8sskoskogggg8k8c0k-113621254093  Started
2024-Nov-19 11:36:57.995506
Error response from daemon: driver failed programming external connectivity on endpoint weatherapi-xcw0ow8sskoskogggg8k8c0k-113621252084 (58c0d5378b42a9e3ad1bc7b85a3a94315865b31ee9f5ab3411667f612a4dc331): Bind for 0.0.0.0:10001 failed: port is already allocated

[hades200082]

Aspirate did make some changes to support compose build from dokerfile.

It might be possible now?

With aspire 9 they also ship an image for the aspire dashboard.

When you deploy to azure with azd cli it also gives you that dashboard.

[hades200082]

Some other options for supporting native .NET deployments here might be:

• Add .NET 6-9 support to NixPacks
• Utilise .NET's built-in containerization publishing (you can publish a container without a dockerfile!)