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

dotnet-runtime: no compatible versions #19

Open
jromero opened this issue Sep 8, 2021 · 1 comment
Open

dotnet-runtime: no compatible versions #19

jromero opened this issue Sep 8, 2021 · 1 comment

Comments

@jromero
Copy link

jromero commented Sep 8, 2021

kpdemo populate yields some build failures. It looks like the current setup can no longer support .net.

failed to satisfy "dotnet-runtime" dependency for stack "io.buildpacks.stacks.bionic" with version constraint "2.1.0": no compatible versions. Supported versions are: [3.1.17, 3.1.18, 5.0.8, 5.0.9]
Paketo .NET Core Runtime Buildpack 0.2.0
  Resolving Dotnet Core Runtime version
    Candidate version sources (in priority order):
      runtimeconfig.json -> "2.1.0"

    No exact version match found; attempting version roll-forward
@bayardwest
Copy link

bayardwest commented Dec 22, 2023

We ran into this as well with an Azure Container Registry (ACR) pack command after upgrading a project from .NET 6.0 to .NET 8.0. In our case, we were running the command in the same directory as the project (.csproj) file when we needed to be a level higher where the solution (.sln) file was located. Previous versions of .NET tolerated that.

Using Azure pipelines, it may be more convenient to pass in ../. as the working directory as in:
az acr pack build --registry <<someregistryname>> --image testimage --pull --builder cloudfoundry/cnb ../.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants