[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Ruby-ex deployment times out

Hey Gerard,

I also hit this issue this morning:

Seems that a recent change to docker (projectatomic/docker) introduced
a regression:

$ git describe

$ git log --oneline a612434.. | grep -i digest
8e24cc3 Merge pull request #194 from runcom/backport-pulldigests-fedora
6c0bb14 Do not show empty tags for digest references in output
a216b04 Treat digest only images as dangling
34771e8 Always store the image digest when pulling and pushing an image.

I'm thinking 34771e8, though I've yet to prove it.

You can go to koji and downgrade to an old version (this is the one I used):

I've opened a bug to track this:


On Thu, Sep 29, 2016 at 11:47 AM, Andy Goldstein <agoldste redhat com> wrote:
> cc Seth, who has done some more investigation and will reply with an update.
> Andy
> On Wed, Sep 28, 2016 at 11:30 AM, Gerard Braad <me gbraad nl> wrote:
>> On Wed, Sep 28, 2016 at 11:22 PM, Michail Kargakis <mkargaki redhat com>
>> wrote:
>> > You can work around this by pulling by tag instead of by hash. Try
>> > setting
>> > {DOCKER-REGISTRY-IP}/myproject/ruby-ex:latest instead of
>> > {DOCKER-REGISTRY-IP}/myproject/ruby-ex sha256:... in your DC.
>> > Not sure how pull by hash can be fixed though.
>> Unfortunately, the image is not available as mentioned before:
>> # docker pull
>> Trying to pull repository ...
>> Pulling repository
>> Error: image myproject/ruby-ex not found

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]