Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Create knownissues.adoc #314

Merged
merged 4 commits into from
Feb 26, 2020
Merged

Create knownissues.adoc #314

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d0522c4
Create knownissues.adoc
jantley-ibm Feb 25, 2020
75bcb12
per Matt's review
jantley-ibm Feb 25, 2020
90247be
couple more
jantley-ibm Feb 25, 2020
ca8019e
one last one
jantley-ibm Feb 25, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions ref/general/reference/knownissues.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
:page-layout: doc
:page-doc-category: Reference
:linkattrs:
:sectanchors:
= Known issues

Be aware of the following issues that can cause problems for your instance of Kabanero.

== Build pipelines fail when collection is active

Versions 0.5.5 and 0.5.6 of the Appsody CLI add a prefix of the default image registry, docker.io, to the image tag in a new application configuration, regardless of whether the base collection specifies it. This action results in an application configuration that conflicts with the metadata that is 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 because it appears the relevant collection is not active within the Kabanero instance.

After you initialize 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, upgrade your Appsody CLI to the latest version.