Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create: always offer to pull #875

Closed
wants to merge 0 commits into from
Closed

create: always offer to pull #875

wants to merge 0 commits into from

Conversation

juhp
Copy link
Contributor

@juhp juhp commented Sep 13, 2021

This PR addresses 2 common user issues with toolbox create:

  • users need to manually download newer images themselves
  • the hardcoded "500MB download" is misleading

I have tested this locally and it seems to work okay for me.

@softwarefactory-project-zuul
Copy link

Build succeeded.

@juhp
Copy link
Contributor Author

juhp commented Oct 15, 2021

Any feedback on this?
It is quite small :)

src/cmd/create.go Outdated Show resolved Hide resolved
@softwarefactory-project-zuul
Copy link

Build failed.

@juhp
Copy link
Contributor Author

juhp commented Nov 16, 2021

So how about this Download <<image>> (image size ~400MB) then. Any better?

@softwarefactory-project-zuul
Copy link

Build failed.

@juhp
Copy link
Contributor Author

juhp commented Nov 16, 2021

An alternative for the pull part could be to make it an option instead:

ie toolbox create --pull ...

That would make it opt-in which should alleviate the storage space concerns with pulling newer images.
(Personally I would prefer to offer to pull by default since it is too easy to forget to pull,
but at least having the command option makes it more visible and easy to update.
It might be nice to add a purge command eventually specifically for removing obsolete toolbox images.)

Though in it's current form the user can already say "no" to downloading a newer image: they are prompted each time.

@juhp juhp requested a review from debarshiray November 16, 2021 09:16
@debarshiray
Copy link
Member

So how about this Download <<image>> (image size ~400MB) then.
Any better?

Well, the best option would be to comment on containers/skopeo#641 and push for it to get prioritized. It's not entirely trivial to get the exact size of the image.

@juhp
Copy link
Contributor Author

juhp commented Nov 17, 2021

Okay, sure, thank you for the detailed replies and clarity: let's drop the size part of this PR completely.

(Actually I had not realized that skopeo was only exposing local image sizes.)

@juhp juhp changed the title create: always offer to pull and don't mention 500MB create: always offer to pull Nov 17, 2021
@softwarefactory-project-zuul
Copy link

Build failed.

@sgallagher
Copy link

Any hope of reviving this PR? It would vastly simplify the documentation on how to upgrade the Developer Toolbox I maintain, for instance.

Copy link

Build succeeded.
https://softwarefactory-project.io/zuul/t/local/buildset/f52aae5400a542dfb3972981e359fd43

✔️ unit-test SUCCESS in 5m 33s
✔️ unit-test-migration-path-for-coreos-toolbox SUCCESS in 3m 33s
✔️ unit-test-restricted SUCCESS in 5m 25s
✔️ system-test-fedora-rawhide SUCCESS in 38m 19s
✔️ system-test-fedora-40 SUCCESS in 36m 37s
✔️ system-test-fedora-39 SUCCESS in 36m 01s
✔️ system-test-fedora-38 SUCCESS in 35m 45s

@juhp
Copy link
Contributor Author

juhp commented Jul 10, 2024

I made my main branch current, which caused this PR to close - not that it was going anywhere...

Anyway you can still find my original proposal in 8bfbbf4 in (https://github.com/juhp/toolbox/tree/always-pull)
(I think that was it basically)

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