Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Operator] -registry seems to be ignored, upgrade image always pulled from docker.io

See original GitHub issue

This is a…


[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report  
[ ] Documentation issue or request

The problem

When -registry argument is used in the operator image, it seems to be ignored. We have currently fuse-online-operator:1.1-4 image that specifies our docker registry:

"Entrypoint": [
                "/usr/local/bin/syndesis-operator",
                "-template",
                "/conf/syndesis-template.yml",
                "-registry",
                "registry.access.redhat.com"
            ]

but when the operator tries to upgrade 7.0.1 to 7.1, it tries to pull the image from docker hub:

Failed to pull image "docker.io/fuse7/fuse-ignite-upgrade:1.1-8": rpc error: code = Unknown desc = Error: image fuse7/fuse-ignite-upgrade:1.1-8 not found

I tried to modify the upstream 1.4.7 operator image to specify my own registry:

FROM syndesis/syndesis-operator:1.4.7

ENTRYPOINT [ "/usr/local/bin/syndesis-operator", "-template", "/conf/syndesis-template.yml", "-registry", "myregistry" ]

and after deploying that image, it still pulls docker.io.

Expected behavior

To pull from repository that is specified in -registry

Screenshot

Request and Response Data

API Endpoints and Schemas

Tasks involved / Steps to Reproduce

Issue Analytics

State:
Created 5 years ago
Comments:11 (6 by maintainers)

Top GitHub Comments

1reaction

nicolaferrarocommented, Aug 30, 2018

I’ve fixed it in https://github.com/syndesisio/fuse-online-install (branch master and 1.4.x) by removing the command, in order to use the entrypoint of the productized image. If this works (@avano, cc: @djcoleman), we can close this.

We need also to update the yaml file in this repo (not relevant for Fuse installation, but they better stay in sync).

0reactions

avanocommented, Aug 31, 2018

looks good to me 😃

Top Results From Across the Web

Configuring a registry - Docker Documentation

In a typical setup where you run your Registry from the official image, ... ignore: mediatypes: - application/octet-stream actions: - pull redis: addr: ......

Deprecated Engine Features - Docker Documentation

Pulling images from non-compliant image registries . Deprecated in Release: v20.10. Docker Engine v20.10 and up includes optimizations to verify if images in ......

docker manifest - Docker Documentation

A manifest list is a list of image layers that is created by specifying one or more (ideally more than one) image names....

Test an insecure registry - Docker Documentation

With insecure registries enabled, Docker goes through the following steps: First, try using HTTPS. If HTTPS is available but the certificate is invalid,...

HTTP API V2 - Docker Documentation

The first step in pulling an image is to retrieve the manifest. For reference, the relevant manifest fields for the registry are the...