Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    HTTP 500 When pushing docker image

    Scheduled Pinned Locked Moved Support
    14 Posts 2 Posters 25 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W Offline
      wechselberg.nisboerge_3629
      last edited by

      Hi,

      when pushing one image to the ProGet Server we get a HTTP 500 error.

      16:00:45  + docker push vl-dev-repo.ki.lan/sst-coco-oci-prod/sub-coco-cli:test
16:00:45  The push refers to repository [vl-dev-repo.ki.lan/sst-coco-oci-prod/sub-coco-cli]
16:00:45  5476da93a45d: Preparing
16:00:45  94cff3c0f1ca: Preparing
16:00:45  26e17999f588: Preparing
16:00:45  3668ef704aa2: Preparing
16:00:45  8248b221e3e1: Preparing
16:00:45  9e3250a6c86c: Preparing
16:00:45  1d76ae469fc3: Preparing
16:00:45  0168265636e1: Preparing
16:00:45  53cd28cbdad5: Preparing
16:00:45  43d0adb5e44f: Preparing
16:00:45  cca10bba424a: Preparing
16:00:45  d3fd88d75ece: Preparing
16:00:45  d157eb985080: Preparing
16:00:45  974a466e1a0a: Preparing
16:00:45  3819aa7bbe8b: Preparing
16:00:45  4c13ea2c0b02: Preparing
16:00:45  2ed6a19677f5: Preparing
16:00:45  d2f7abddd607: Preparing
16:00:45  53babe930602: Preparing
16:00:45  9e3250a6c86c: Waiting
16:00:45  1d76ae469fc3: Waiting
16:00:45  0168265636e1: Waiting
16:00:45  53cd28cbdad5: Waiting
16:00:45  43d0adb5e44f: Waiting
16:00:45  cca10bba424a: Waiting
16:00:45  2ed6a19677f5: Waiting
16:00:45  d3fd88d75ece: Waiting
16:00:45  d2f7abddd607: Waiting
16:00:45  53babe930602: Waiting
16:00:45  d157eb985080: Waiting
16:00:45  974a466e1a0a: Waiting
16:00:45  3819aa7bbe8b: Waiting
16:00:45  4c13ea2c0b02: Waiting
16:00:45  3668ef704aa2: Layer already exists
16:00:45  26e17999f588: Layer already exists
16:00:45  8248b221e3e1: Layer already exists
16:00:45  1d76ae469fc3: Layer already exists
16:00:45  9e3250a6c86c: Layer already exists
16:00:45  0168265636e1: Layer already exists
16:00:45  53cd28cbdad5: Layer already exists
16:00:45  43d0adb5e44f: Layer already exists
16:00:45  cca10bba424a: Layer already exists
16:00:45  d3fd88d75ece: Layer already exists
16:00:45  d157eb985080: Layer already exists
16:00:45  974a466e1a0a: Layer already exists
16:00:45  94cff3c0f1ca: Pushed
16:00:45  3819aa7bbe8b: Layer already exists
16:00:45  4c13ea2c0b02: Layer already exists
16:00:45  d2f7abddd607: Layer already exists
16:00:45  2ed6a19677f5: Layer already exists
16:00:57  53babe930602: Retrying in 5 seconds

16:01:20  53babe930602: Retrying in 1 second
16:01:30  5476da93a45d: Pushed
16:01:32  53babe930602: Retrying in 15 seconds
[...]
16:02:13  53babe930602: Retrying in 1 second
16:02:23  received unexpected HTTP status: 500 Internal Server Error

      In the container logs we can see:

      info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/32b375c9-b883-4836-8aa7-49fc1f849ada - 202 0 - 8424.9972ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/32b375c9-b883-4836-8aa7-49fc1f849ada?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - - 0
A 500 error occurred in sst-coco-oci-prod: Nullable object must have a value.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/32b375c9-b883-4836-8aa7-49fc1f849ada?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - 500 1091 application/json 38.1785ms

      We had a similar issue in the past, which seemed to be fixed with version 25.0.10, but it now reappeared.
      I updated to 25.0.12 now, but the issue existed in 25.0.10 as well as in 25.0.12.

      atrippA 1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer @wechselberg.nisboerge_3629
        last edited by

        Hi @wechselberg-nisboerge_3629 ,

        This is definitely a strange error; are you using PostgreSQL by chance?

        I'm seeing 53babe930602: Retrying... a few times. Is this consistently happening with this layer? Is there anything special about it (big, small, etc)?

        Thanks,
        Alana

        1 Reply Last reply Reply Quote 0
        • W Offline
          wechselberg.nisboerge_3629
          last edited by wechselberg.nisboerge_3629

          Hi,

          I am using a setup that is pretty much consistent with your quickstart.
          Linux Host and ProGet running in Container. I think it is Postgres in there, yes.

          Regarding the layer: I will check with the team. (I am just the guy in IT ;) )

          Regards,
          Nis

          EDIT:
          So ... this is the whole Dockerfile that is built and uploaded here:

          FROM vl-dev-repo.ki.lan/sst-devops-oci-prod/sub-coco-nodejs:latest

WORKDIR /cococli

RUN wget https://vl-jenkins-ctl.ki.lan/job/Coco/job/Coco/job/main/lastSuccessfulBuild/artifact/cococli-linux.tar.gz && \
    tar xzf cococli-linux.tar.gz && \
    rm -rf cococli-linux.tar.gz && \
    ln -sf /cococli/cococli /usr/bin/cococli

          The vl-dev-repo is the ProGet and the base image is in ProGet just fine.

          atrippA 1 Reply Last reply Reply Quote 0
          • atrippA Offline
            atripp inedo-engineer @wechselberg.nisboerge_3629
            last edited by

            @wechselberg-nisboerge_3629 thanks for comfirming!

            Any chance you can get more entries from the container log? It'd be really helpful to see more requests going back/forth. This is just such a strange behavior given the seeming simplicity of your image

            Also, there should be an option, in ProGet 2025.12, to enable web logging (Admin > HTTPS Logging); it's a brand new feature, but it writes logs to a log file.

            1 Reply Last reply Reply Quote 0
            • W Offline
              wechselberg.nisboerge_3629
              last edited by

              I tried activating the HTTP Request logging, but I get another HTTP 500 here ...

              Running Execution Dispatcher...
Checking for executions to dispatch...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/administration/web-server/http-settings/configure - application/x-www-form-urlencoded 328
Attempting to update shared configuration for ProGet.
Attempting to use shared configuration for ProGet.
Shared configuration file not found at /etc/inedo/ProGet.config.
An error occurred in the web application: Cannot load shared configuration for ProGet.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/administration/web-server/http-settings/configure - 500 2521 text/html;+charset=UTF-8 43.0276ms

              (Obviously out of scope/unrelated here, but wanted to let you know about that)

              What kind of logs are helpful from the container log?

              atrippA 1 Reply Last reply Reply Quote 0
              • atrippA Offline
                atripp inedo-engineer @wechselberg.nisboerge_3629
                last edited by

                @wechselberg-nisboerge_3629 the main thing I'm looking for is the HTTP access logs - we have 1.5 Entires before (PATCH-finish, PUT-Start, PUT-finish), so seeing more would be really helpful.

                What's odd is seeing the "retrying..."

                1 Reply Last reply Reply Quote 0
                • W Offline
                  wechselberg.nisboerge_3629
                  last edited by

                  There you go ... this should be the complete log of pushing that image.

                  Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/ - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/ - 401 145 application/json 2.4781ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/_auth?account=deployment&client_id=docker&offline_token=true&service=vl-dev-repo.ki.lan - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/_auth?account=deployment&client_id=docker&offline_token=true&service=vl-dev-repo.ki.lan - 200 369 application/json 32.8540ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/ - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/ - 200 47 text/plain 3.3824ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/ - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/ - 401 145 application/json 0.7435ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/_auth?account=deployment&scope=repository%3Asst-coco-oci-prod%2Fsub-coco-cli%3Apush%2Cpull&service=vl-dev-repo.ki.lan - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET http://vl-dev-repo.ki.lan/v2/_auth?account=deployment&scope=repository%3Asst-coco-oci-prod%2Fsub-coco-cli%3Apush%2Cpull&service=vl-dev-repo.ki.lan - 200 369 application/json 34.7176ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 22.3339ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 20.6079ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 31.6916ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 20.2714ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ed7f4055-d456-4767-a568-8bcb9e4dae22 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/73fb2122-6cdd-4de1-a22e-a3fb26ba98e8 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/f81b6fbd-ad19-4961-87b0-a222f8d65577 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 53.3528ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/645157d8-8c16-402f-a968-c2778b39a6ed - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/f81b6fbd-ad19-4961-87b0-a222f8d65577 - 202 0 - 11.0440ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/645157d8-8c16-402f-a968-c2778b39a6ed - 202 0 - 10.1261ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/7c2c3611-2a39-4f48-8e8a-7bdf09899bae - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/7c2c3611-2a39-4f48-8e8a-7bdf09899bae - 202 0 - 8.5752ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/645157d8-8c16-402f-a968-c2778b39a6ed?digest=sha256%3Acb8670ad004ff5f0321e07da367e229a4808cff21969b0dd8c9447c32931c05e - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/f81b6fbd-ad19-4961-87b0-a222f8d65577?digest=sha256%3Ac10a323c75f48a3f7f63938c250c034414d4fbf111a68c52197b9026821f46fd - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/7c2c3611-2a39-4f48-8e8a-7bdf09899bae?digest=sha256%3A5a16507c304ed7ba2f1dec16bc412897126c6fc69ecbcee5fb8ed8457e0bddfd - - 0
Attempting to open blob cb8670ad004f (id=10128)...
Successfully opened blob cb8670ad004f (id=10128) as .tar.gz file. Starting scan...
Attempting to open blob c10a323c75f4 (id=10129)...
Successfully opened blob c10a323c75f4 (id=10129) as .tar.gz file. Starting scan...
Attempting to open blob 5a16507c304e (id=10130)...
Successfully opened blob 5a16507c304e (id=10130) as .tar.gz file. Starting scan...
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/7c2c3611-2a39-4f48-8e8a-7bdf09899bae?digest=sha256%3A5a16507c304ed7ba2f1dec16bc412897126c6fc69ecbcee5fb8ed8457e0bddfd - 201 0 - 60.3794ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/645157d8-8c16-402f-a968-c2778b39a6ed?digest=sha256%3Acb8670ad004ff5f0321e07da367e229a4808cff21969b0dd8c9447c32931c05e - 201 0 - 75.1990ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/f81b6fbd-ad19-4961-87b0-a222f8d65577?digest=sha256%3Ac10a323c75f48a3f7f63938c250c034414d4fbf111a68c52197b9026821f46fd - 201 0 - 66.9033ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:5a16507c304ed7ba2f1dec16bc412897126c6fc69ecbcee5fb8ed8457e0bddfd - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:c10a323c75f48a3f7f63938c250c034414d4fbf111a68c52197b9026821f46fd - - -
The blob at http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:5a16507c304ed7ba2f1dec16bc412897126c6fc69ecbcee5fb8ed8457e0bddfd does not have a media type associated with it. This may be fixed by the feed cleanup task for sst-coco-oci-prod.
The blob at http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:c10a323c75f48a3f7f63938c250c034414d4fbf111a68c52197b9026821f46fd does not have a media type associated with it. This may be fixed by the feed cleanup task for sst-coco-oci-prod.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:5a16507c304ed7ba2f1dec16bc412897126c6fc69ecbcee5fb8ed8457e0bddfd - 200 265 application/octet-stream 22.6717ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:c10a323c75f48a3f7f63938c250c034414d4fbf111a68c52197b9026821f46fd - 200 205 application/octet-stream 7.3281ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:cb8670ad004ff5f0321e07da367e229a4808cff21969b0dd8c9447c32931c05e - - -
The blob at http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:cb8670ad004ff5f0321e07da367e229a4808cff21969b0dd8c9447c32931c05e does not have a media type associated with it. This may be fixed by the feed cleanup task for sst-coco-oci-prod.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:cb8670ad004ff5f0321e07da367e229a4808cff21969b0dd8c9447c32931c05e - 200 96 application/octet-stream 4.9245ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:a81f7bd97d92549642734fdf878f3ecc7b89ecd72aae22204f6c24c9fd083704 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:a81f7bd97d92549642734fdf878f3ecc7b89ecd72aae22204f6c24c9fd083704 - 200 10000654 application/vnd.docker.image.rootfs.diff.tar.gzip 5.1725ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:54b03df36d446a1163f86210f518ca113c233a084cfe8f5a9f3a9c8ad566c8cb - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:bfa3d3e4cf7f9dd27246d40ceed05dc4d28bfeeb80324ea51bac2d401d5a13c4 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:54b03df36d446a1163f86210f518ca113c233a084cfe8f5a9f3a9c8ad566c8cb - 200 3430 application/vnd.docker.image.rootfs.diff.tar.gzip 5.5336ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:bfa3d3e4cf7f9dd27246d40ceed05dc4d28bfeeb80324ea51bac2d401d5a13c4 - 200 10372462 application/vnd.docker.image.rootfs.diff.tar.gzip 6.9847ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:e332af79be02415dcaf296fb7e257c3e43d851a3f51cd52f78a770d10e103cd5 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:e332af79be02415dcaf296fb7e257c3e43d851a3f51cd52f78a770d10e103cd5 - 200 15175983 application/vnd.docker.image.rootfs.diff.tar.gzip 6.8531ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:9157c33488042e7d75b36a4eb15ae02627cacd714c4c7212259c8c1352561121 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:0649e381bf819b1e0f8e86dfbc29c873931462b256cc6414b27c8d67fb4699cb - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:9157c33488042e7d75b36a4eb15ae02627cacd714c4c7212259c8c1352561121 - 200 127149 application/vnd.docker.image.rootfs.diff.tar.gzip 5.0431ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:0649e381bf819b1e0f8e86dfbc29c873931462b256cc6414b27c8d67fb4699cb - 200 2071 application/vnd.docker.image.rootfs.diff.tar.gzip 5.5343ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:14cd97ab0673a50082bf7f2d053208a526479b6e0c13549d808e815d61ba9700 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:14cd97ab0673a50082bf7f2d053208a526479b6e0c13549d808e815d61ba9700 - 200 1771 application/vnd.docker.image.rootfs.diff.tar.gzip 5.6797ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:7337869f5d805b82847d243a3197299987bad8712bf1265d420e26d60862b859 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:788f4e8602eea4b058237b3c20c834b3997f2fac3c573666c2a0c384f2e99419 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:7337869f5d805b82847d243a3197299987bad8712bf1265d420e26d60862b859 - 200 1686 application/vnd.docker.image.rootfs.diff.tar.gzip 7.0375ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:788f4e8602eea4b058237b3c20c834b3997f2fac3c573666c2a0c384f2e99419 - 200 260 application/vnd.docker.image.rootfs.diff.tar.gzip 6.3954ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:775a325bc2aa2aa75e855af154839b397d850e14c927204905e3f46f718ffb58 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:775a325bc2aa2aa75e855af154839b397d850e14c927204905e3f46f718ffb58 - 200 446 application/vnd.docker.image.rootfs.diff.tar.gzip 7.6769ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:00f4ac723d07c76a3aa3f6744387791188f5d413214d80addff94a5732b559b9 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:00f4ac723d07c76a3aa3f6744387791188f5d413214d80addff94a5732b559b9 - 200 1250736 application/vnd.docker.image.rootfs.diff.tar.gzip 4.9155ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:8dcb664baf87e9bb932e2663beb0221ce0375a0b2d9b59c0ca8d771801e3aafb - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:8dcb664baf87e9bb932e2663beb0221ce0375a0b2d9b59c0ca8d771801e3aafb - 200 55780645 application/vnd.docker.image.rootfs.diff.tar.gzip 6.2385ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:28432cc975ed52ac2085f9db91a57f9696424f6cff7703086464fd1a8220b63e - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:353e14e5cc47664fba714a7da288001d90427c705494847ac773f5cc08199451 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:28432cc975ed52ac2085f9db91a57f9696424f6cff7703086464fd1a8220b63e - 200 3326 application/vnd.docker.image.rootfs.diff.tar.gzip 5.2463ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:353e14e5cc47664fba714a7da288001d90427c705494847ac773f5cc08199451 - 200 211352566 application/vnd.docker.image.rootfs.diff.tar.gzip 4.4519ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:255774e0027b72d2327719e78dbad5ad8c9cf446d055e45be7fc149418470bae - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:255774e0027b72d2327719e78dbad5ad8c9cf446d055e45be7fc149418470bae - 200 64396484 application/vnd.docker.image.rootfs.diff.tar.gzip 5.6129ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:7cd785773db44407e20a679ce5439222e505475eed5b99f1910eb2cda51729ab - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:091eb8249475f42de217265c501e0186f0a3ea7490ef7f51458c30db91fb3cac - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:7cd785773db44407e20a679ce5439222e505475eed5b99f1910eb2cda51729ab - 404 158 application/json 4.9299ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:091eb8249475f42de217265c501e0186f0a3ea7490ef7f51458c30db91fb3cac - 200 24011136 application/vnd.docker.image.rootfs.diff.tar.gzip 4.5069ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 6.9731ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/bc45b2de-d284-44d7-9707-197c69acc199 - - -
Running Multipart Upload Cleanup...
Multipart Upload Cleanup completed.
Running Execution Dispatcher...
Checking for executions to dispatch...
Execution Dispatcher completed.
Running Connector Cache Check...
Getting list of connector responses...
Connector Cache Check completed.
Running Docker Upload Cleanup...
Docker Upload Cleanup completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/bc45b2de-d284-44d7-9707-197c69acc199 - 202 0 - 11030.2968ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/bc45b2de-d284-44d7-9707-197c69acc199?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - - 0
A 500 error occurred in sst-coco-oci-prod: Nullable object must have a value.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/bc45b2de-d284-44d7-9707-197c69acc199?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - 500 1054 application/json 28.3463ms
Running Node Message Cleanup...
Purging processed node messages and messages older than 10/20/2025 11:14:51...
No messages to purge.
Node Message Cleanup completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 12.3959ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/85b1b98a-4fe4-4b96-b94e-c5601f0479cf - - -
Running Feed Replication...
Feed Replication completed.
Running Drop Path Monitor...
Getting list of feeds with a drop path...
No feeds with a drop path.
Drop Path Monitor completed.
Running Execution Dispatcher...
Checking for executions to dispatch...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/73fb2122-6cdd-4de1-a22e-a3fb26ba98e8 - 202 0 - 24188.0247ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/73fb2122-6cdd-4de1-a22e-a3fb26ba98e8?digest=sha256%3Af4da01d28713fb9c6cca713ab630ad93131d2b25b47d954b0b13e49c1837cee4 - - 0
Created execution (id=6144) to scan uploaded blob (id=10131).
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/73fb2122-6cdd-4de1-a22e-a3fb26ba98e8?digest=sha256%3Af4da01d28713fb9c6cca713ab630ad93131d2b25b47d954b0b13e49c1837cee4 - 201 0 - 32.2901ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:f4da01d28713fb9c6cca713ab630ad93131d2b25b47d954b0b13e49c1837cee4 - - -
The blob at http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:f4da01d28713fb9c6cca713ab630ad93131d2b25b47d954b0b13e49c1837cee4 does not have a media type associated with it. This may be fixed by the feed cleanup task for sst-coco-oci-prod.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:f4da01d28713fb9c6cca713ab630ad93131d2b25b47d954b0b13e49c1837cee4 - 200 320734315 application/octet-stream 6.2105ms
Running Service Heartbeat...
Service Heartbeat completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/85b1b98a-4fe4-4b96-b94e-c5601f0479cf - 202 0 - 10991.9175ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/85b1b98a-4fe4-4b96-b94e-c5601f0479cf?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - - 0
A 500 error occurred in sst-coco-oci-prod: Nullable object must have a value.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/85b1b98a-4fe4-4b96-b94e-c5601f0479cf?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - 500 1054 application/json 47.9726ms
Running Execution Dispatcher...
Checking for executions to dispatch...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 14.0346ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ce08b054-2649-4aa6-84e9-39bf25f44de5 - - -
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ed7f4055-d456-4767-a568-8bcb9e4dae22 - 202 0 - 46200.1078ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ed7f4055-d456-4767-a568-8bcb9e4dae22?digest=sha256%3Adb022c43a487cf61b704c7ae6bde238cc12230ce863706b38c1c075d0ad33f1f - - 0
Created execution (id=6145) to scan uploaded blob (id=10132).
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ed7f4055-d456-4767-a568-8bcb9e4dae22?digest=sha256%3Adb022c43a487cf61b704c7ae6bde238cc12230ce863706b38c1c075d0ad33f1f - 201 0 - 26.2197ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:db022c43a487cf61b704c7ae6bde238cc12230ce863706b38c1c075d0ad33f1f - - -
The blob at http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:db022c43a487cf61b704c7ae6bde238cc12230ce863706b38c1c075d0ad33f1f does not have a media type associated with it. This may be fixed by the feed cleanup task for sst-coco-oci-prod.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 HEAD http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/sha256:db022c43a487cf61b704c7ae6bde238cc12230ce863706b38c1c075d0ad33f1f - 200 322376036 application/octet-stream 7.3476ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ce08b054-2649-4aa6-84e9-39bf25f44de5 - 202 0 - 10843.0526ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ce08b054-2649-4aa6-84e9-39bf25f44de5?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - - 0
A 500 error occurred in sst-coco-oci-prod: Nullable object must have a value.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ce08b054-2649-4aa6-84e9-39bf25f44de5?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - 500 1054 application/json 41.3446ms
Running Execution Dispatcher...
Checking for executions to dispatch...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - - 0
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 POST http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/ - 202 0 - 16.6565ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/cdf84034-5bb6-460a-b3f9-1a904adb6482 - - -
Running Execution Dispatcher...
Checking for executions to dispatch...
Execution Dispatcher completed.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PATCH http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/cdf84034-5bb6-460a-b3f9-1a904adb6482 - 202 0 - 10810.0643ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/cdf84034-5bb6-460a-b3f9-1a904adb6482?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - - 0
A 500 error occurred in sst-coco-oci-prod: Nullable object must have a value.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 PUT http://vl-dev-repo.ki.lan/v2/sst-coco-oci-prod/sub-coco-cli/blobs/uploads/cdf84034-5bb6-460a-b3f9-1a904adb6482?digest=sha256%3A10af00adc39beb81a045806ad9605cea669cf8deb097de90d0aa1bdc21ea1342 - 500 1054 application/json 38.5128ms
Running Feed Replication...
Feed Replication completed.
Running Drop Path Monitor...
Getting list of feeds with a drop path...
No feeds with a drop path.
Drop Path Monitor completed.
                  atrippA 1 Reply Last reply Reply Quote 0
                  • atrippA Offline
                    atripp inedo-engineer @wechselberg.nisboerge_3629
                    last edited by

                    Thanks @wechselberg-nisboerge_3629 , Exactly what I was looking for!

                    Can you provide some more information about this image? Basically I'm trying to find the layer / mediatype / size. I believe these commands will do it:

                    docker image inspect vl-dev-repo.ki.lan/sst-coco-oci-prod/sub-coco-cli:test --format '{{json .RootFS.Layers}}' | jq .

docker history vl-dev-repo.ki.lan/sst-coco-oci-prod/sub-coco-cli:test

                    Thanks,
                    Alana

                    1 Reply Last reply Reply Quote 0
                    • W Offline
                      wechselberg.nisboerge_3629
                      last edited by

                      I bolted the commands on the end of the build-pipeline (didn't have jq there, so no pretty-print :( )

                      11:10:30  [Pipeline] sh
11:10:30  + docker image inspect vl-dev-repo.ki.lan/sst-coco-oci-prod/sub-coco-cli:test --format {{json .RootFS.Layers}}
11:10:30  ["sha256:53babe930602419c46727120034c3748ae023bef28f10edb018fbcfbcedbc0e8","sha256:d2f7abddd607612ee919b0d3fffe9f156b3165b215b1dae105b4b2be4888a285","sha256:2ed6a19677f5e5d6bc7ca58dc86e0c9e54c894bdfff537014736c168d82a856d","sha256:4c13ea2c0b021f7e71473290da414fe79371abf7b4de411c0a70fd2fc88916d5","sha256:3819aa7bbe8b8cfb77bf83601325f3dc827bdbc64f78ae94f32f9e395442219f","sha256:974a466e1a0a72939963ab5a5a1580ce2a9b64f6d679b024b1743e75cc98230b","sha256:d157eb985080f7a3c669f603504170acd6a9baa8bfac41766892748036817c89","sha256:d3fd88d75eceb26175fafa209666edb8302a2e8dfd67a67d4be5ca0de8e4faf1","sha256:cca10bba424a8deca74801a7eb42bd0c839799fd0c8459fa78708b3f08623f58","sha256:43d0adb5e44f71e0bb1df06cbcc2bce0ccc0c561f69c08e709cb645ed6d14f79","sha256:53cd28cbdad5958f78dbe989e11f10ad00af2070a8124389f512dfe7c01acc0b","sha256:0168265636e1485223359bee8c72a8aa1f466f533ae8c8a43c4238bbc8eef7ec","sha256:1d76ae469fc3af7a1fd0798410d282829a196a9eaa0e3267bf60874875ba2cdf","sha256:9e3250a6c86cd5d73d391e1f231025dd989f6af6779199164b0cdfb79e8e0759","sha256:8248b221e3e18728da753498526c4d75a46be425cd93e6bf9ab9431e19c46e4a","sha256:3668ef704aa2d2cc16d3373f4dfb576774a54240318539d918d7c20f57ba8347","sha256:26e17999f588641253aeb6af523cedb95a26a811d8810e4755aa207f47a9783a","sha256:7ea1b636426fc1500000c18be0b2e84de3e03d03e464fc92dc1a13041ceb3e2b","sha256:e2bb05d10eeb435d22b656376240b35679cb969457e9903c584f413265019f06","sha256:329bbc7a67d5df391507eec1f89a6307a665537ce07bb05e7718387cc1bc9554","sha256:a5bcb84c6d8473dc057ebdbc117dfa277e92c4ec32a87794ba22f97a81945400","sha256:69861b96a589a98a3350ed875b98d2b84a43f1fb755a34601ada1c7bd1a1d480"]
11:10:30  [Pipeline] sh
11:10:31  + docker history vl-dev-repo.ki.lan/sst-coco-oci-prod/sub-coco-cli:test
11:10:31  IMAGE          CREATED              CREATED BY                                      SIZE      COMMENT
11:10:31  a3d0d487318a   About a minute ago   /bin/sh -c #(nop)  LABEL workaround=proget-l…   0B        
11:10:31  86bbac677558   About a minute ago   /bin/sh -c ln -sf /cococli/cococli /usr/bin/…   124B      
11:10:31  86e04a62e7a1   About a minute ago   /bin/sh -c rm -f cococli-linux.tar.gz     &&…   92B       
11:10:31  c2588ecd1b75   About a minute ago   /bin/sh -c tar xzf cococli-linux.tar.gz     …   570MB     
11:10:31  42c88c0b8978   2 minutes ago        /bin/sh -c wget https://vl-jenkins-ctl.ki.la…   321MB     
11:10:31  5cb1d530be17   2 minutes ago        /bin/sh -c #(nop) WORKDIR /cococli              0B        
11:10:31  cda64ca915f5   6 months ago         /bin/sh -c npm config set registry 'http://k…   28.2MB    
11:10:31  <missing>      6 months ago         /bin/sh -c adduser --uid 1001 --disabled-pas…   9.31kB    
11:10:31  <missing>      6 months ago         /bin/sh -c apt-get -y dist-upgrade              31.8MB    
11:10:31  <missing>      6 months ago         /bin/sh -c apt-get update                       19.6MB    
11:10:31  <missing>      6 months ago         /bin/sh -c #(nop)  ENV NODE_EXTRA_CA_CERTS=/…   0B        
11:10:31  <missing>      6 months ago         /bin/sh -c update-ca-certificates               221kB     
11:10:31  <missing>      6 months ago         /bin/sh -c #(nop) COPY file:7b70afc5e5853dd4…   2.5kB     
11:10:31  <missing>      6 months ago         /bin/sh -c #(nop) COPY file:2d71c9b2684db523…   2.18kB    
11:10:31  <missing>      6 months ago         /bin/sh -c #(nop) COPY file:e896d850409c67fa…   1.92kB    
11:10:31  <missing>      6 months ago         /bin/sh -c #(nop) COPY file:aaf45b8891f3d7c7…   166B      
11:10:31  <missing>      6 months ago         /bin/sh -c #(nop)  ENV no_proxy=*.ads.local,…   0B        
11:10:31  <missing>      6 months ago         /bin/sh -c #(nop)  ENV https_proxy=http://fw…   0B        
11:10:31  <missing>      6 months ago         /bin/sh -c #(nop)  ENV http_proxy=http://fw0…   0B        
11:10:31  <missing>      8 months ago         CMD ["node"]                                    0B        buildkit.dockerfile.v0
11:10:31  <missing>      8 months ago         ENTRYPOINT ["docker-entrypoint.sh"]             0B        buildkit.dockerfile.v0
11:10:31  <missing>      8 months ago         COPY docker-entrypoint.sh /usr/local/bin/ # …   388B      buildkit.dockerfile.v0
11:10:31  <missing>      8 months ago         RUN /bin/sh -c set -ex   && export GNUPGHOME…   5.34MB    buildkit.dockerfile.v0
11:10:31  <missing>      8 months ago         ENV YARN_VERSION=1.22.22                        0B        buildkit.dockerfile.v0
11:10:31  <missing>      8 months ago         RUN /bin/sh -c ARCH= && dpkgArch="$(dpkg --p…   185MB     buildkit.dockerfile.v0
11:10:31  <missing>      8 months ago         ENV NODE_VERSION=22.14.0                        0B        buildkit.dockerfile.v0
11:10:31  <missing>      8 months ago         RUN /bin/sh -c groupadd --gid 1000 node   &&…   8.94kB    buildkit.dockerfile.v0
11:10:31  <missing>      21 months ago        RUN /bin/sh -c set -ex;  apt-get update;  ap…   588MB     buildkit.dockerfile.v0
11:10:31  <missing>      21 months ago        RUN /bin/sh -c set -eux;  apt-get update;  a…   177MB     buildkit.dockerfile.v0
11:10:31  <missing>      2 years ago          RUN /bin/sh -c set -eux;  apt-get update;  a…   48.4MB    buildkit.dockerfile.v0
11:10:31  <missing>      2 years ago          # debian.sh --arch 'amd64' out/ 'bookworm' '…   117MB     debuerreotype 0.15

                      The layers that are <missing> are part of the base image, that is in proget already, so they should be fine.

                      atrippA 1 Reply Last reply Reply Quote 0
                      • atrippA Offline
                        atripp inedo-engineer @wechselberg.nisboerge_3629
                        last edited by

                        Hi @wechselberg-nisboerge_3629 ,

                        Thanks for sharing that; sadly I'm still at a total loss here 🙄

                        But I did make a change that I think should work, or at least give us a different error.... can you try upgrading to inedo/proget:25.0.14-ci.7?

                        The change is in that build. OF course, you can easily downgrade later.

                        Thanks,
                        Alana

                        1 Reply Last reply Reply Quote 0
                        • W Offline
                          wechselberg.nisboerge_3629
                          last edited by

                          @atripp said in HTTP 500 When pushing docker image:

                          can you try upgrading to inedo/proget:25.0.14-ci.7?

                          I can't find that image in the registry. Is this the right version?

                          atrippA 1 Reply Last reply Reply Quote 0
                          • atrippA Offline
                            atripp inedo-engineer @wechselberg.nisboerge_3629
                            last edited by

                            @wechselberg-nisboerge_3629 can you check it out again? Should be there now :)

                            W 1 Reply Last reply Reply Quote 0
                            • W Offline
                              wechselberg.nisboerge_3629 @atripp
                              last edited by

                              @atripp Indeed, it is there now.

                              I updated to 25.0.14-ci.7 and the docker push went through now. No error anymore.

                              Not sure if your change did it or the gods of randomness caused the Docker build to do something slightly different and make it push now ...

                              But thanks for the support.

                              atrippA 1 Reply Last reply Reply Quote 0
                              • atrippA Offline
                                atripp inedo-engineer @wechselberg.nisboerge_3629
                                last edited by

                                @wechselberg-nisboerge_3629 great news, thanks! Well it'll be in the upcoming release (2025.13) in that case :)

                                1 Reply Last reply Reply Quote 0

                                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                With your input, this post could be even better 💗

                                Register Login
                                • 1 / 1
                                • First post
                                  Last post
                                Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation