Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. aslepikas_5779
    A
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    aslepikas_5779

    @aslepikas_5779

    0
    Reputation
    6
    Posts
    1
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    aslepikas_5779 Follow

    Best posts made by aslepikas_5779

    This user hasn't posted anything yet.

    Latest posts made by aslepikas_5779

    • RE: docker pull from proget not working

      @atripp

      5.2.27 has fixed the issue. Thank you so much!

      posted in Support
      A
      aslepikas_5779
    • RE: docker pull from proget not working

      @atripp

      I did update proget manually, I built my own docker image for 5.2.25, deployed it, same issue (that version did fix the helm 3 support that I was waiting for as well). Today I've updated to 5.2.26, same 500 issue as before.

      
      Message: 
      A 500 error occurred in (unknown feed): The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.
      
      Details: 
      URL: http://proget.mywebsite.com/v2/myapp/manifests/1.0.0
      Referrer: (not set)
      User: (unknown)
      User Agent: docker/19.03.5 go/go1.12.12 git-commit/633a0ea kernel/4.19.76-linuxkit os/linux arch/amd64 UpstreamClient(Docker-Client/19.03.5 \(windows\))
      Stack trace:
      

      if you know where proget puts the logs in the linux container or a way to set the standard out more verbosely so I can get a better stack-trace for your guys, let me know.

      posted in Support
      A
      aslepikas_5779
    • RE: docker pull from proget not working

      @ben

      yeah, the stacktrace is empty

      01aac804-4b91-4d6e-8cdb-8135810bfb10-image.png

      posted in Support
      A
      aslepikas_5779
    • RE: docker pull from proget not working

      @ben

      I updated to 5.2.25 where PG-1669 was fixed. This still appears to be an issue, same warning as above, only difference is the User Agent field

      User Agent: docker/19.03.3 go/go1.12.10 git-commit/a872fc2 kernel/4.4.0-165-generic os/linux arch/amd64 UpstreamClient(Docker-Client/19.03.3 \(linux\))
      
      posted in Support
      A
      aslepikas_5779
    • Helm 3 support

      Currently I cannot upload helm 3 (apiVersion: v2 in chart.yaml) to the feed.

      When I attempt to push through the UI I get the following message:

      The file you uploaded is not a Helm chart.
      
      Please select a new file and try again.
      

      attempting to do through powershell I get

      Invoke-WebRequest : Helm chart apiVersion "v2" does not match expected value 
      "v1".
      

      We just started using helm after helm 3 came out so all our charts are apiVersion:v2, no tiller component, all clientside, so it made our lives a lot easier. but we cannot upload or use our charts so it'd be nice if proget supported it.

      here's a guide on what's changed if needed, but I would imagine it's as easy as including "v2" apiVersion.

      posted in Support
      A
      aslepikas_5779
    • RE: docker pull from proget not working

      I'm getting the same issue. Output from diagnostic center is :

      A 500 error occurred in (unknown feed): The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.
      
      URL: http://proget.mywebsite.com/v2/docker/myapp/manifests/1.0.0
      Referrer: (not set)
      User: (unknown)
      User Agent: docker/19.03.2 go/go1.12.8 git-commit/6a30dfc kernel/4.4.0-170-generic os/linux arch/amd64 UpstreamClient(Docker-Client/19.03.2 \(linux\))
      Stack trace:
      
      posted in Support
      A
      aslepikas_5779