Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@runcom
Copy link
Member

@runcom runcom commented Sep 17, 2016

This is tackling image management operations from #8.
This work is based on containers/image#63 by vendoring @nalind's branch add-storage-transport here and by applying and modifying some of his patches from his ocid branch at https://github.com/nalind/ocid/tree/storage-tests.

The last commits add images pull and delete functionalities like so:

$ sudo ./ocic images pull kubernetes/pause
$ sudo ./ocic images list
INFO[0000] id:"93a58c47ea25244e199de35f752ed7f91c25ce96947792d51fad48e0b26a2fb3" repo_tags:"kubernetes/pause:latest"
$ sudo ./ocic images delete kubernetes/pause:latest
$ sudo ./ocic images list
$ # empty list

Plan is:

This might not be perfect as a whole when taking into account containers rootfs management but it's a start - at least in the direction of image management. Containers' rootfs management will come as part of another PR since this is already huge.

/cc @nalind @mrunalp PTAL

@nalind if you want to carry this please do so - I opened it so we have a WIP branch everyone can test and look around. Also opened this to avoid you re-vendoring everything and rebasing.

@runcom runcom changed the title Storage in Image Management [WIP] Storage in Image Management Sep 17, 2016
// Set up a connection to the server.
conn, err := getClientConnection()
if err != nil {
return fmt.Errorf("Failed to connect: %v", err)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Failed -> failed. We probably need to fix this all over the code.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will, probably going to submit a separate PR

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done here, I'm submitting a separate PR for the other cases

@mrunalp
Copy link
Member

mrunalp commented Sep 17, 2016

Nice! I will test and review in more detail.

@runcom
Copy link
Member Author

runcom commented Sep 17, 2016

@mrunalp great, I haven't tested everything yet on the image management side, will probably do so tomorrow or Monday as I implement the remaining client calls related to images.

@runcom runcom force-pushed the storage branch 2 times, most recently from 22b7b96 to 0ebd399 Compare September 18, 2016 09:05
@runcom
Copy link
Member Author

runcom commented Sep 18, 2016

added image list and delete functionalities to the cli

runcom and others added 6 commits September 19, 2016 12:45
Flesh out the implementations of various image-related functions.

Signed-off-by: Nalin Dahyabhai <[email protected]>
Signed-off-by: Antonio Murdaca <[email protected]>
Signed-off-by: Antonio Murdaca <[email protected]>
Signed-off-by: Antonio Murdaca <[email protected]>
@rhatdan
Copy link
Contributor

rhatdan commented Oct 7, 2016

Any movement on this?

@runcom
Copy link
Member Author

runcom commented Oct 7, 2016

@rhatdan this will surely need a rebase now that we use another vendoring tool - I think @nalind has been working on this.

@runcom
Copy link
Member Author

runcom commented Nov 3, 2016

@nalind is gonna take this and re-open it. Closing.

@runcom runcom closed this Nov 3, 2016
@runcom runcom deleted the storage branch November 3, 2016 14:41
jwcesign referenced this pull request in jwcesign/cri-o May 1, 2022
bumping knative.dev/hack 11d193b...b284d49:
  > b284d49 fix the latest_version function (# 101)
  > 42a2ccb Release use `knative-vX.Y.Z` tag and infer go module tag version automatically (# 98)
  > a42c72a Update community files (# 95)
  > 810ab22 Make go_update_deps module-release aware (# 93)
  > f1228dd Update community files (# 90)

Signed-off-by: Knative Automation <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants