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!

Docker Feed Connector to registry.gitlab.com fails



  • Hey,

    I am trying to setup a Docker connector to registry.gitlab.com and the connector is failing with the below exception. I have entered the correct username/password and can successfully login using 'docker login registry.gitlab.com' command.

    Newtonsoft.Json.JsonSerializationException: Required property 'access_token' not found in JSON. Path '', line 1, position 1082.
    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EndProcessProperty(Object newObject, JsonReader reader, JsonObjectContract contract, Int32 initialDepth, JsonProperty property, PropertyPresence presence, Boolean setDefaultValue)
    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
    at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
    at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
    at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
    at Inedo.ProGet.Feeds.Docker.DockerConnector.<GetDirectResponseAsync>d__2.MoveNext()
    

    Steps to Reproduce:

    1. Add a Docker Feed
    2. Add a Connector to the Feed from step 1
    3. Add 'https://registry.gitlab.com' under the Connection URL
    4. Add 'registry.gitlab.com' under connection name
    5. Add the correct username/password (same used for accessing https://gitlab.com/explore )
    6. Observe under Diagnostic Center, Connector health checks post the above exception for this Connector.

    Product: ProGet
    Version: 5.0.13


  • inedo-engineer

    This is a result of the bug described here: PG-1308



  • Thanks for the quick update John. Definitely looking forward to the 5.1 release now, once it is out of Beta.



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation