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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Application is crashing and getting the permission denied after deploying the DotNet app. #3184

Closed
mukeshcpande opened this issue Mar 19, 2024 · 10 comments
Closed

[Bug]: Application is crashing and getting the permission denied after deploying the DotNet app. #3184

mukeshcpande opened this issue Mar 19, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@mukeshcpande
Copy link

mukeshcpande commented Mar 19, 2024 •
edited
Loading

What happened?

Published the dotnet app with target framework 6 with the following command
dotnet publish "C:\gitRepo\SampleAsp\SampleAsp.csproj" -c release --self-contained -r linux-x64 --output "C:\gitRepo\SampleAsp\output"

After publish when deploying the app getting following error as

16:54:31.11-0500 [STG/] OUT paketo-buildpacks/icu 0.7.7
2024-03-18T16:54:31.11-0500 [STG/] OUT paketo-buildpacks/dotnet-execute 0.14.29
2024-03-18T16:54:31.11-0500 [STG/] OUT Timer: Detector ran for 44.385842ms and ended at 2024-03-18T21:54:31Z
2024-03-18T16:54:31.95-0500 [STG/] OUT Warning: No cached data will be used, no cache specified.
2024-03-18T16:54:31.95-0500 [STG/] OUT Timer: Restorer started at 2024-03-18T21:54:31Z
2024-03-18T16:54:31.95-0500 [STG/] OUT Timer: Restorer ran for 127.492µs and ended at 2024-03-18T21:54:31Z
2024-03-18T16:54:33.43-0500 [STG/] OUT Timer: Builder started at 2024-03-18T21:54:33Z
2024-03-18T16:54:33.44-0500 [STG/] OUT
2024-03-18T16:54:33.44-0500 [STG/] OUT Paketo Buildpack for CA Certificates 3.6.8
2024-03-18T16:54:33.44-0500 [STG/] OUT https://github.com/paketo-buildpacks/ca-certificates
2024-03-18T16:54:33.44-0500 [STG/] OUT Launch Helper: Contributing to layer
2024-03-18T16:54:33.44-0500 [STG/] OUT Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper
2024-03-18T16:54:33.46-0500 [STG/] OUT Paketo Buildpack for ICU 0.7.7
2024-03-18T16:54:33.46-0500 [STG/] OUT Resolving ICU version
2024-03-18T16:54:33.46-0500 [STG/] OUT Candidate version sources (in priority order):
2024-03-18T16:54:33.46-0500 [STG/] OUT -> ""
2024-03-18T16:54:33.46-0500 [STG/] OUT
2024-03-18T16:54:33.46-0500 [STG/] OUT Selected ICU version (using ): 74.2
2024-03-18T16:54:33.46-0500 [STG/] OUT
2024-03-18T16:54:33.46-0500 [STG/] OUT Executing build process
2024-03-18T16:54:33.46-0500 [STG/] OUT Installing ICU
2024-03-18T16:54:34.22-0500 [STG/] OUT Completed in 762ms
2024-03-18T16:54:34.22-0500 [STG/] OUT
2024-03-18T16:54:34.22-0500 [STG/] OUT Generating SBOM for /layers/paketo-buildpacks_icu/icu
2024-03-18T16:54:34.22-0500 [STG/] OUT Completed in 0s
2024-03-18T16:54:34.22-0500 [STG/] OUT
2024-03-18T16:54:34.24-0500 [STG/] OUT Paketo Buildpack for .NET Execute 0.14.29
2024-03-18T16:54:34.24-0500 [STG/] OUT Generating SBOM for /workspace
2024-03-18T16:54:34.28-0500 [STG/] OUT Completed in 36ms
2024-03-18T16:54:34.28-0500 [STG/] OUT
2024-03-18T16:54:34.28-0500 [STG/] OUT Assigning launch processes:
2024-03-18T16:54:34.28-0500 [STG/] OUT SampleAsp (default): /workspace/SampleAsp
2024-03-18T16:54:34.28-0500 [STG/] OUT
2024-03-18T16:54:34.31-0500 [STG/] OUT Timer: Builder ran for 873.043637ms and ended at 2024-03-18T21:54:34Z
2024-03-18T16:54:37.15-0500 [STG/] OUT Warning: No cached data will be used, no cache specified.
2024-03-18T16:54:37.36-0500 [STG/] OUT Timer: Exporter started at 2024-03-18T21:54:37Z
2024-03-18T16:54:37.39-0500 [STG/] OUT Adding layer 'paketo-buildpacks/ca-certificates:helper'
2024-03-18T16:54:37.65-0500 [STG/] OUT Adding layer 'paketo-buildpacks/icu:icu'
2024-03-18T16:54:38.89-0500 [STG/] OUT Adding layer 'paketo-buildpacks/dotnet-execute:port-chooser'
2024-03-18T16:54:38.96-0500 [STG/] OUT Adding layer 'buildpacksio/lifecycle:launch.sbom'
2024-03-18T16:54:42.62-0500 [STG/] OUT Adding 1/1 app layer(s)
2024-03-18T16:54:42.69-0500 [STG/] OUT Adding layer 'buildpacksio/lifecycle:launcher'
2024-03-18T16:54:42.83-0500 [STG/] OUT Adding layer 'buildpacksio/lifecycle:config'
2024-03-18T16:54:42.83-0500 [STG/] OUT Adding layer 'buildpacksio/lifecycle:process-types'
2024-03-18T16:54:42.83-0500 [STG/] OUT Adding label 'io.buildpacks.lifecycle.metadata'
2024-03-18T16:54:42.83-0500 [STG/] OUT Adding label 'io.buildpacks.build.metadata'
2024-03-18T16:54:42.83-0500 [STG/] OUT Adding label 'io.buildpacks.project.metadata'
2024-03-18T16:54:42.83-0500 [STG/] OUT Setting default process type 'SampleAsp'
2024-03-18T16:54:42.83-0500 [STG/] OUT Timer: Saving harbor.dell.com/pcf-images/korifi/kob/d32428c9-a580-481e-addb-4120701596be-droplets... started at 2024-03-18T21:54:42Z
2024-03-18T16:54:45.32-0500 [STG/] OUT *** Images (sha256:396b002694907ea1a79a5448ead1948651616089632b0f210fc6fe1bb9aaae9a):
2024-03-18T16:54:45.32-0500 [STG/] OUT harbor.dell.com/pcf-images/korifi/kob/d32428c9-a580-481e-addb-4120701596be-droplets
2024-03-18T16:54:45.32-0500 [STG/] OUT harbor.dell.com/pcf-images/korifi/kob/d32428c9-a580-481e-addb-4120701596be-droplets:b1.20240318.215420
2024-03-18T16:54:45.32-0500 [STG/] OUT Timer: Saving harbor.dell.com/pcf-images/korifi/kob/d32428c9-a580-481e-addb-4120701596be-droplets... ran for 2.486000673s and ended at 2024-03-18T21:54:45Z
2024-03-18T16:54:45.32-0500 [STG/] OUT Timer: Exporter ran for 7.953359261s and ended at 2024-03-18T21:54:45Z
2024-03-18T16:54:46.40-0500 [STG/] OUT Build successful
2024-03-18T16:55:09.82-0500 [APP/] OUT Setting ASPNETCORE_URLS=http://0.0.0.0:8080
2024-03-18T16:55:09.83-0500 [APP/] OUT ERROR: failed to launch: path lookup: exec: "/workspace/SampleAsp": permission denied

What you expected to happen

Contents from the publish directory for the dotnet app should get deployed successfully and run without any crash along with the permission issue.

Acceptance Criteria

GIVEN : Build and Publish, when deploying the app
WHEN I : After deployment start of the app
THEN I : Crash with the permission denied error

How to reproduce it (as minimally and precisely as possible)

Create any sample hello world app, build and publish per above given command and deploy the contents of the output directory in the container.

Anything else we need to know?

No response

Environment

Revision of codebase:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:
@mukeshcpande mukeshcpande added the bug Something isn't working label Mar 19, 2024
@github-project-automation github-project-automation bot moved this to 🧊 Icebox in Korifi - Backlog Mar 19, 2024
@danail-branekov
Copy link
Member

Hey @mukeshcpande

We are not fluent in dotnet, could you please provide a sample application that we could just start playing with?

Also, korifi does not come with the dotnet buildpack by default, how did you install it?

As per the error you are seeing:

2024-03-18T16:55:09.83-0500 [APP/] OUT ERROR: failed to launch: path lookup: exec: "/workspace/SampleAsp": permission denied

It could be that the buildpack building the app image is not setting proper permission on the executable, i.e. it might be an issue with the dotnet buildpack.

@mukeshcpande
Copy link
Author

mukeshcpande commented Mar 28, 2024 •
edited
Loading

Hi @danail-branekov ,

Those are samples given in the below repo and you can use either 'fdd-app' or 'fde-app' and can deploy the published contains as is to see the 'permission denied' error message

https://github.com/paketo-buildpacks/samples/tree/main/dotnet-core/aspnet

'fdd-app' - https://github.com/paketo-buildpacks/samples/tree/main/dotnet-core/fdd-app

'fde-app' - github.com/paketo-buildpacks/samples/tree/main/dotnet-core/fde-app

//////log trace//////
2024-03-27T17:03:07.98-0500 [APP/] OUT Setting ASPNETCORE_URLS=http://0.0.0.0:8080/
2024-03-27T17:03:07.98-0500 [APP/] OUT ERROR: failed to launch: path lookup: exec: "/workspace/aspnet": permission denied

@danail-branekov
Copy link
Member

Hmm, seems to be working for me.

I could not use fda-app and fde-app as they do not have their csproj file which seems to be required by dotnet publish. I used https://github.com/paketo-buildpacks/samples/tree/main/dotnet-core/aspnet

So here is how it looks on my side:

  • publish
/workspace/samples/dotnet-core/aspnet main
 dotnet publish
SBuild version 17.8.5+b5265ef37 for .NET
 Determining projects to restore...
 All projects are up-to-date for restore.
 aspnet -> /home/ccloud/workspace/samples/dotnet-core/aspnet/bin/Debug/net6.0/aspnet.dll
 aspnet -> /home/ccloud/workspace/samples/dotnet-core/aspnet/bin/Debug/net6.0/publish/
  • push
❯ cf push aspnet -p ./bin/Debug/net6.0/publish
....
   Timer: Cache ran for 1.107484ms and ended at 2024-03-28T17:10:07Z
   Build successful

Waiting for app aspnet to start...

Instances starting...
Instances starting...
Instances starting...
Instances starting...

name:              aspnet
requested state:   started
routes:            aspnet.apps-127-0-0-1.nip.io
last uploaded:     Thu 28 Mar 17:09:46 UTC 2024
stack:             io.buildpacks.stacks.jammy
buildpacks:

type:           web
sidecars:
instances:      1/1
memory usage:   1024M
     state     since                  cpu    memory   disk     logging      details
#0   running   2024-03-28T17:10:16Z   0.0%   0 of 0   0 of 0   0/s of 0/s
  • listing apps:
❯ cf apps
Getting apps in org org / space space as cf-admin...

name     requested state   processes             routes
aspnet   started           web:1/1, aspnet:0/0   aspnet.apps-127-0-0-1.nip.io
  • curling
~/workspace/samples/dotnet-core/aspnet main
❯ curl -k https://aspnet.apps-127-0-0-1.nip.io
<!DOCTYPE html>
<html>
  <head>
    <title>Powered By Paketo Buildpacks</title>
  </head>
  <body>
    <img style="display: block; margin-left: auto; margin-right: auto; width: 50%;" src="https://paketo.io/images/paketo-logo-full-color
  </body>
</html>
  • logs
❯ cf logs aspnet --recent
Retrieving logs for app aspnet in org org / space space as cf-admin...
...
  2024-03-28T17:10:07.85+0000 [STG/] OUT *** Images (sha256:1dc2ea8a6a714e416ea847374f56056982788c236181462785e8b01e6e11292e):
  2024-03-28T17:10:07.85+0000 [STG/] OUT       localregistry-docker-registry.default.svc.cluster.local:30050/25fb152b-2dba-4a26-a88a-656b4b680053-droplets
  2024-03-28T17:10:07.85+0000 [STG/] OUT       localregistry-docker-registry.default.svc.cluster.local:30050/25fb152b-2dba-4a26-a88a-656b4b680053-droplets:
  2024-03-28T17:10:07.85+0000 [STG/] OUT Timer: Saving localregistry-docker-registry.default.svc.cluster.local:30050/25fb152b-2dba-4a26-a88a-656b4b680053-d
 ended at 2024-03-28T17:10:07Z
  2024-03-28T17:10:07.85+0000 [STG/] OUT Timer: Exporter ran for 5.685046336s and ended at 2024-03-28T17:10:07Z
  2024-03-28T17:10:07.85+0000 [STG/] OUT Timer: Cache started at 2024-03-28T17:10:07Z
  2024-03-28T17:10:07.85+0000 [STG/] OUT Timer: Cache ran for 1.107484ms and ended at 2024-03-28T17:10:07Z
  2024-03-28T17:10:08.85+0000 [STG/] OUT Build successful
  2024-03-28T17:10:14.16+0000 [APP/] OUT Setting ASPNETCORE_URLS=http://0.0.0.0:8080
  2024-03-28T17:10:14.37+0000 [APP/] OUT info: Microsoft.Hosting.Lifetime[14]
  2024-03-28T17:10:14.37+0000 [APP/] OUT       Now listening on: http://0.0.0.0:8080
  2024-03-28T17:10:14.37+0000 [APP/] OUT info: Microsoft.Hosting.Lifetime[0]
  2024-03-28T17:10:14.37+0000 [APP/] OUT       Application started. Press Ctrl+C to shut down.
  2024-03-28T17:10:14.37+0000 [APP/] OUT info: Microsoft.Hosting.Lifetime[0]
  2024-03-28T17:10:14.37+0000 [APP/] OUT       Hosting environment: Production
  2024-03-28T17:10:14.37+0000 [APP/] OUT info: Microsoft.Hosting.Lifetime[0]
  2024-03-28T17:10:14.37+0000 [APP/] OUT       Content root path: /workspace

I am using gcr.io/paketo-buildpacks/dotnet-core as buildpack image.

Am I missing something?

@mukeshcpande
Copy link
Author

mukeshcpande commented Mar 28, 2024 •
edited
Loading

Hi @danail-branekov,

Following app contents are already the published directory contents and that's why you're not seeing the '*.csproj'

'fdd-app' - https://github.com/paketo-buildpacks/samples/tree/main/dotnet-core/fdd-app

'fde-app' - https://github.com/paketo-buildpacks/samples/tree/main/dotnet-core/fde-app

You can try deploying them directly from the above paths.

Could you please try command "dotnet publish -c release -r linux-x64" followed by push and let us know the output?

Our output while deploying where issue is happening when we go with the runtime command as '-r linux-x64'

2024-03-28T16:18:53.97-0500 [STG/] OUT Assigning launch processes:
2024-03-28T16:18:53.97-0500 [STG/] OUT WebApi (default): /workspace/WebApi

and ending up with the error
ERROR: failed to launch: path lookup: exec: "/workspace/WebApi": permission denied

If we go with the simple publish command like how you tried above, will work for us as well "dotnet publish -c release" and deployment traces are,

2024-03-28T16:16:09.63-0500 [STG/] OUT Assigning launch processes:
2024-03-28T16:16:09.63-0500 [STG/] OUT WebApi (default): dotnet /workspace/WebApi.dll

@danail-branekov
Copy link
Member

Thank you for the details, @mukeshcpande

Using dotnet publish -c release --self-contained -r linux-x64 makes pushing the app succeed as well:

  • publish:

~/workspace/samples/dotnet-core/aspnet
❯ dotnet publish -c release --self-contained  -r linux-x64
MSBuild version 17.8.5+b5265ef37 for .NET
  Determining projects to restore...
  All projects are up-to-date for restore.
  aspnet -> /home/ccloud/workspace/samples/dotnet-core/aspnet/bin/release/net6.0/linux-x64/aspnet.dll
  aspnet -> /home/ccloud/workspace/samples/dotnet-core/aspnet/bin/release/net6.0/linux-x64/publish/
  • push

~/workspace/samples/dotnet-core/aspnet
❯ cf push aspnet -p ./bin/release/net6.0/linux-x64/publish
Pushing app aspnet to org org / space space as cf-admin...
Packaging files to upload...
Uploading files...
 41.64 MiB / 41.64 MiB [==========================================================================================================================================================================================================================] 100.00% 6s

Waiting for API to complete processing files...

Staging app and tracing logs...

   Build reason(s): CONFIG
   CONFIG:
        + env:
        + - name: VCAP_SERVICES
        +   valueFrom:
        +     secretKeyRef:
        +       key: VCAP_SERVICES
        +       name: 44f7fad1-0519-4c7f-b386-9e4c64446e43-vcap-services
        + - name: VCAP_APPLICATION
        +   valueFrom:
        +     secretKeyRef:
        +       key: VCAP_APPLICATION
        +       name: 44f7fad1-0519-4c7f-b386-9e4c64446e43-vcap-application
        resources: {}
        - source: {}
        + source:
        +   registry:
        +     image: localregistry-docker-registry.default.svc.cluster.local:30050/44f7fad1-0519-4c7f-b386-9e4c64446e43-packages@sha256:c53194c6e21796866f31ca3f68beb0663d9b59c5edc05d4fa28afa4d825ee940
        +     imagePullSecrets:
        +     - name: image-registry-credentials
   Loading registry credentials from service account secrets
   Loading secret for "localregistry-docker-registry.default.svc.cluster.local:30050" from secret "image-registry-credentials" at location "/var/build-secrets/image-registry-credentials"
   Loading cluster credential helpers
   Pulling localregistry-docker-registry.default.svc.cluster.local:30050/44f7fad1-0519-4c7f-b386-9e4c64446e43-packages@sha256:c53194c6e21796866f31ca3f68beb0663d9b59c5edc05d4fa28afa4d825ee940...
   Successfully pulled localregistry-docker-registry.default.svc.cluster.local:30050/44f7fad1-0519-4c7f-b386-9e4c64446e43-packages@sha256:c53194c6e21796866f31ca3f68beb0663d9b59c5edc05d4fa28afa4d825ee940 in path "/workspace"
   Timer: Analyzer started at 2024-03-29T09:44:51Z
   Image with name "localregistry-docker-registry.default.svc.cluster.local:30050/44f7fad1-0519-4c7f-b386-9e4c64446e43-droplets" not found
   Timer: Analyzer ran for 333.89962ms and ended at 2024-03-29T09:44:51Z
   Timer: Detector started at 2024-03-29T09:44:52Z
   ======== Output: paketo-buildpacks/[email protected] ========
   could not find app in /workspace: expected one of server.js | app.js | main.js | index.js
   err:  paketo-buildpacks/[email protected] (1)
   ======== Output: paketo-buildpacks/[email protected] ========
   could not find app in /workspace: expected one of server.js | app.js | main.js | index.js
   err:  paketo-buildpacks/[email protected] (1)
   ======== Output: paketo-buildpacks/[email protected] ========
   could not find app in /workspace: expected one of server.js | app.js | main.js | index.js
   err:  paketo-buildpacks/[email protected] (1)
   3 of 12 buildpacks participating
   paketo-buildpacks/ca-certificates 3.6.8
   paketo-buildpacks/icu             0.7.8
   paketo-buildpacks/dotnet-execute  0.14.30
   Timer: Detector ran for 182.02769ms and ended at 2024-03-29T09:44:52Z
   Timer: Restorer started at 2024-03-29T09:44:53Z
   Timer: Restorer ran for 153.542µs and ended at 2024-03-29T09:44:53Z
   Timer: Builder started at 2024-03-29T09:44:54Z

   Paketo Buildpack for CA Certificates 3.6.8
     https://github.com/paketo-buildpacks/ca-certificates
     Launch Helper: Contributing to layer
       Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper
   Paketo Buildpack for ICU 0.7.8
     Resolving ICU version
       Candidate version sources (in priority order):
         <unknown> -> ""

       Selected ICU version (using <unknown>): 74.2

     Executing build process
       Installing ICU
         Completed in 867ms

     Generating SBOM for /layers/paketo-buildpacks_icu/icu
         Completed in 0s

   Paketo Buildpack for .NET Execute 0.14.30
     Generating SBOM for /workspace
         Completed in 32ms

     Assigning launch processes:
       aspnet (default): /workspace/aspnet

   Timer: Builder ran for 949.12743ms and ended at 2024-03-29T09:44:55Z
   Timer: Exporter started at 2024-03-29T09:44:57Z
   Adding layer 'paketo-buildpacks/ca-certificates:helper'
   Adding layer 'paketo-buildpacks/icu:icu'
   Adding layer 'paketo-buildpacks/dotnet-execute:port-chooser'
   Adding layer 'buildpacksio/lifecycle:launch.sbom'
   Adding 1/1 app layer(s)
   Adding layer 'buildpacksio/lifecycle:launcher'
   Adding layer 'buildpacksio/lifecycle:config'
   Adding layer 'buildpacksio/lifecycle:process-types'
   Adding label 'io.buildpacks.lifecycle.metadata'
   Adding label 'io.buildpacks.build.metadata'
   Adding label 'io.buildpacks.project.metadata'
   Setting default process type 'aspnet'
   Timer: Saving localregistry-docker-registry.default.svc.cluster.local:30050/44f7fad1-0519-4c7f-b386-9e4c64446e43-droplets... started at 2024-03-29T09:45:00Z
   *** Images (sha256:462f1c62ecb8c3bb80a2dde3f99cffcd1692251ab7549e5af6e202dfd96ce576):
         localregistry-docker-registry.default.svc.cluster.local:30050/44f7fad1-0519-4c7f-b386-9e4c64446e43-droplets
         localregistry-docker-registry.default.svc.cluster.local:30050/44f7fad1-0519-4c7f-b386-9e4c64446e43-droplets:b1.20240329.094442
   Timer: Saving localregistry-docker-registry.default.svc.cluster.local:30050/44f7fad1-0519-4c7f-b386-9e4c64446e43-droplets... ran for 2.139907051s and ended at 2024-03-29T09:45:02Z
   Timer: Exporter ran for 5.512516978s and ended at 2024-03-29T09:45:02Z
   Timer: Cache started at 2024-03-29T09:45:02Z
   Timer: Cache ran for 516.306µs and ended at 2024-03-29T09:45:02Z
   Build successful

Waiting for app aspnet to start...

Instances starting...
Instances starting...
Instances starting...
Instances starting...

name:              aspnet
requested state:   started
routes:            aspnet.apps-127-0-0-1.nip.io
last uploaded:     Fri 29 Mar 09:44:42 UTC 2024
stack:             io.buildpacks.stacks.jammy
buildpacks:

type:           web
sidecars:
instances:      1/1
memory usage:   1024M
     state     since                  cpu    memory   disk     logging      details
#0   running   2024-03-29T09:45:10Z   0.0%   0 of 0   0 of 0   0/s of 0/s

type:            aspnet
sidecars:
instances:       0/0
memory usage:    1024M
start command:   /workspace/aspnet
There are no running instances of this process.

Note that the build output on my side says:

     Assigning launch processes:
       aspnet (default): /workspace/aspnet

This seems to be a bit different from what you see, I wonder how that makes a difference.

  • listing apps
❯ cf apps
Getting apps in org org / space space as cf-admin...

name     requested state   processes             routes
aspnet   started           web:1/1, aspnet:0/0   aspnet.apps-127-0-0-1.nip.io
  • curiling:
❯ curl -k https://aspnet.apps-127-0-0-1.nip.io
<!DOCTYPE html>
<html>
  <head>
    <title>Powered By Paketo Buildpacks</title>
  </head>
  <body>
    <img style="display: block; margin-left: auto; margin-right: auto; width: 50%;" src="https://paketo.io/images/paketo-logo-full-color.png"></img>
  </body>
</html>

Could you provide a full list of commands that you are running?

I noticed that you are probably using Windows, I wonder whether that makes a difference.

@mukeshcpande
Copy link
Author

Hi @danail-branekov,

Looks like you're pulling the image from "Pulling localregistry-docker-registry.default.svc.cluster.local:30050", are you adding the Dockerfile while doing the publish or doing publish alone without any extra files?

Yes I'm publishing on windows machine followed by deployment.
Could you please confirm which OS you're using?

@danail-branekov
Copy link
Member

danail-branekov commented Mar 29, 2024 •
edited
Loading

The local registry is just an oci registry running locally on the cluster, it could be anything else, e.g. dockerhub or Google artifact registry. We are not putting the dockerfile there ourselves, it is Korifi pushing the app image that is produced by packeto buildpacks as part of the cf push command.

We are running the commands above on Ubuntu against a local kind cluster. We do not have access to windows machines to test there.

@mukeshcpande
Copy link
Author

Hi @danail-branekov
I'm able to create the DotNet app in Ubuntu followed by the successful deployment.
However if we compare CF versus Packeto buildpacks
We're able to run following command followed by successful app deployment from the windows machine with the help CF DotNet core buildpack.

dotnet publish -c release --self-contained -r linux-x64

However if we try the same above command to publish the app image and try to deploy with the Packeto buildpack from windows machine, deployment is getting failed.

What is the difference between buildpacks where one is working fine after publish from the windows/linux machine and other one is unable to work.

@danail-branekov
Copy link
Member

Hey @mukeshcpande

Thanks for the update!

What is the difference between buildpacks where one is working fine after publish from the windows/linux machine and other one is unable to work.

Unfortunately I am not familiar with dotnet and the dotnet buildpack. I would suggest discussing the topic with https://github.com/paketo-buildpacks/dotnet-core (assuming this is the correct buildpack) maintainers.

@mukeshcpande
Copy link
Author

Hi @danail-branekov

Thanks for all your help and will check with the respective team.

@github-project-automation github-project-automation bot moved this from 🧊 Icebox to ✅ Done in Korifi - Backlog Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
Korifi - Backlog
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danail-branekov @mukeshcpande