cerc-io/stack-orchestrator
Archived
12
1
Fork 3
Code Issues 117 Pull Requests 25 Actions Packages Projects Releases 493 Wiki Activity

Stale container images problematic #262

New Issue
Open
opened 2023-03-30 03:48:56 +00:00 by dboreham · 2 comments
dboreham commented 2023-03-30 03:48:56 +00:00
Contributor
Copy Link
Copy Source

I started work on a laptop I haven't used for a few weeks and ran into several strange container build errors that turned out to be due to the docker registry on the machine having old versions of base images. We should add something in stack orchestrator to manage this problem, ideally not requiring hashes of every single reference to a base image everywhere (e.g. some of our transitive dependencies have Dockerfiles that we don't want to have to fork).

I started work on a laptop I haven't used for a few weeks and ran into several strange container build errors that turned out to be due to the docker registry on the machine having old versions of base images. We should add something in stack orchestrator to manage this problem, ideally not requiring hashes of every single reference to a base image everywhere (e.g. some of our transitive dependencies have Dockerfiles that we don't want to have to fork).
AFDudley commented 2023-03-30 03:53:29 +00:00
Owner
Copy Link
Copy Source

FWIW, It seems moderately likely to me that we'll need to store the transitive dependencies in the registry.

FWIW, It seems moderately likely to me that we'll need to store the transitive dependencies in the registry.
dboreham commented 2023-03-30 04:01:03 +00:00
Author
Contributor
Copy Link
Copy Source

Definitely. This is more about the pre-problem of identifying the base images among a big set of containers we build (automatically, not by having a human review them).

We can use the registry to store that metadata and write a tool to update those records when base image updates are published.

Really the docker tooling should do this, but it turns out it was designed to feed you total mystery meat.

Definitely. This is more about the pre-problem of identifying the base images among a big set of containers we build (automatically, not by having a human review them). We can use the registry to store that metadata and write a tool to update those records when base image updates are published. Really the docker tooling should do this, but it turns out it was designed to feed you total mystery meat.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
K8s
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 feature
good first issue
Good for newcomers
 help wanted
Extra attention is needed
 in progress
invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
Copied from Github
An issue or PR manually copied from GitHub.
 Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
AFDudley Alex ashwin cerccicd ericlewis i-norden (Ian Norden) prathamesh (Prathamesh Musale) rachmaninovquar rjk-laconic roysc (Roy Crihfield) srw zramsay
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#262