-
Notifications
You must be signed in to change notification settings - Fork 30
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the problem summary was not entirely accurate. I have suggested an update in my review comments.
|
||
== | ||
|
||
There is a compatibility issue with the Appsody CLI versions 0.5.5 and 0.5.6 that can cause build pipelines to fail. These versions of the Appsody CLI append the image registry to the application configuration in the image tag. This metadata format can conflict with the format that is used in the Kabanero instance. If the applications image is active in the Kabanero instance, the pipeline continues, otherwise the build fails. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Version 0.5.5 and 0.5.6 of the Appsody CLI will prepend the default image registry, docker.io, to the image tag in a new applications configuration regardless of whether the base collection specifies it. This results in an application configuration that conflicts with the meta-data used within the Kabanero instance that was created from the base collection configuration. This conflict causes the default build pipelines to fail for the application as it appears the relevant collection is not active within the Kabanero instance.
|
||
There is a compatibility issue with the Appsody CLI versions 0.5.5 and 0.5.6 that can cause build pipelines to fail. These versions of the Appsody CLI append the image registry to the application configuration in the image tag. This metadata format can conflict with the format that is used in the Kabanero instance. If the applications image is active in the Kabanero instance, the pipeline continues, otherwise the build fails. | ||
|
||
After initializing the application, you can manually edit the `.appsody-config.yaml` file in the application source folder to remove the docker registry portion of the value of the image tag. Alternatively, use a different version of the Appsody CLI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively, upgrade your Appsody CLI to the latest version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.