Body: <p>I have a Spinnaker pipeline which I am trying to add an automated trigger from an ECR repo. Spinnaker lets me add the docker registry as per the following spinnaker <a href="https://www.spinnaker.io/setup/install/providers/docker-registry/#amazon-elastic-container-registry-ecr" rel="nofollow noreferrer">doc link</a>, however I am unable to select an image when setting up the trigger. I've looked around on google and came up short of others having this issue. The closest I found was someone who lost it after an upgrade on a pretty old version. </p>
  
  <p>TDLR: Can't see docker image/repo when adding automated trigger on an ECR repo </p>
  
Comments: CC BY-SA 4.0
Comments: 2019-12-31T01:51:37.450Z
Comments: I just tried specifying the repos as a param and that now has it so I can not see the account at all where I could before
Comments: joshk132
Comments: CC BY-SA 4.0
Comments: 2022-08-08T07:32:29.837Z
Comments: did you ever fix this issue? im also getting this issue
Comments: gdubs
Tags: <docker><cicd><aws-ecr><spinnaker>
Title: Spinnaker not showing images in pipeline trigger
UserDisplayName: joshk132
ThreadText: # Spinnaker not showing images in pipeline trigger
  
  (Asked by: username_0 on 2019-12-31)
  
  I have a Spinnaker pipeline which I am trying to add an automated trigger from an ECR repo. Spinnaker lets me add the docker registry as per the following spinnaker [doc link](https://www.spinnaker.io/setup/install/providers/docker-registry/#amazon-elastic-container-registry-ecr), however I am unable to select an image when setting up the trigger. I've looked around on google and came up short of others having this issue. The closest I found was someone who lost it after an upgrade on a pretty old version.
  
  TDLR: Can't see docker image/repo when adding automated trigger on an ECR repo
  
  **Tags:** docker, cicd, aws-ecr, spinnaker
  
  > **Comments:**
  > **username_0**: I just tried specifying the repos as a param and that now has it so I can not see the account at all where I could before  
  > **username_1**: did you ever fix this issue? im also getting this issue  
  
  ---
  
  ## 0 answers
  
  