Emp deploy spits out error - repository not found

Open psinghsp opened this issue 9 years ago • 1 comments

emp version: 0.11.0

emp deploy aaa/bbb:latest 8076c2c9c0f7: Already exists 821cbea85865: Already exists 9988075fd142: Already exists a324a6bec3a1: Already exists b3551dd2a90d: Already exists fb5529052b48: Already exists 85ece6b79714: Already exists 8fd8bc0523a9: Already exists 4ace38422ffb: Already exists f2844b4085fc: Already exists b8c3f7f324dd: Already exists Pulling repository aaa/bbb error: Repository not found

There is no error message on why this is so. Is there a way to find out what could be happening? Docker local and remote registries both have the "latest" tag.

Nov 28 '16 21:11 psinghsp

Hi @psinghsp. This error can also be returned when you're trying to pull a private image, but the docker client isn't authenticated. Can you verify that you've provided Empire with a .dockercfg to pull credentials from? By default, Empire looks for a file at $HOME/.dockercfg.

Dec 02 '16 01:12 ejholmes