You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an artifact matches a naming convention (like public/taskboot/image*.tar) : it is then downloaded and loaded in our img current state
Blocker: img does not seem to currently support loading tar images (only pull from repositories) See genuinetools/img#226
Alternative: push to a docker repo using a custom tag in Task A, pull from task B/C and tag the image as the required FROM target
The text was updated successfully, but these errors were encountered:
It needs improvement. I rely on the artifact name to match the image name, eg. foo.bar will be pulled to mozillasecurity/foo:latest, instead of reading the manifest to see what it contains.
taskboot need to support the following workflow:
base
base
:final-b
andfinal-c
To build the final images, their task need to have the
base
image in the img local state.So we should add the following logic:
TASK_ID
is set)public/taskboot/image*.tar
) : it is then downloaded and loaded in our img current stateBlocker:
img
does not seem to currently support loading tar images (only pull from repositories) See genuinetools/img#226Alternative: push to a docker repo using a custom tag in Task A, pull from task B/C and tag the image as the required
FROM
targetThe text was updated successfully, but these errors were encountered: