-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.quadlet
Description
Feature request description
Currently there doesn't seem to be support for image pull retry and retry-delay for systemd.unit files.
This is a feature request to add those features.
Suggest potential solution
Support for controlling retries from a systemd unit container file.
Have you considered any alternatives?
No.
Additional context
An example where I have seen an issue is with this unit. The error that I got was:
Trying to pull quay.io/coreos-assembler/coreos-assembler:latest...
Pulling image //quay.io/coreos-assembler/coreos-assembler:latest inside systemd: setting pull timeout to 5m0s
Error: copying system image from manifest list: determining manifest MIME type for docker://quay.io/coreos-assembler/coreos-assembler:latest: reading manifest sha256:9d5c60213547ca29dda408ed4b26313d0d5ff390b9beb0cbdfdc2d6866b33eb9 in quay.io/coreos-assembler/coreos-assembler: received unexpected HTTP status: 502 Bad Gateway
I would expect to be able to configure things such that this error was retried.
The setting pull timeout to 5m0s
suggests the code related to this is in https://github.com/containers/common/blob/34a90afcdc6d30277beeda3988c9a816d15160b9/libimage/copier.go#L378
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.quadlet