-
Bug
-
Resolution: Done-Errata
-
Minor
-
quay-v3.11.0
Some public container image registries(ECR, GCR for example) may generate long passwords for the login.
When this happens, it is not possible to mirror images from those registries in Quay because the password length exceeds the maximum allowed in the Quay database:
\d repomirrorconfig; Table "public.repomirrorconfig" Column | Type | Collation | Nullable | Default ----------------------------+-----------------------------+-----------+----------+---------------------------------------------- id | integer | | not null | nextval('repomirrorconfig_id_seq'::regclass) repository_id | integer | | not null | creation_date | timestamp without time zone | | not null | is_enabled | boolean | | not null | mirror_type | integer | | not null | internal_robot_id | integer | | not null | external_registry_username | character varying(4096) | | | external_registry_password | character varying(4096) | | | external_registry_config | text | | not null | sync_interval | integer | | not null | 60 sync_start_date | timestamp without time zone | | | sync_expiration_date | timestamp without time zone | | | sync_retries_remaining | integer | | not null | 3 sync_status | integer | | not null | sync_transaction_id | character varying(36) | | | root_rule_id | integer | | not null | external_reference | text | | not null |
Changing the data type for the external_registry_password column would be nice to allow our customers to use longer passwords.
- links to
-
RHBA-2024:138800 Red Hat Quay v3.13.0 bug fix release