-
Notifications
You must be signed in to change notification settings - Fork 369
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃摉 Suggestion: add a wiki page about Docker images #9174
Comments
My docker image scripts for running ChromeOS based Chromebrew containers are here: https://gist.github.com/satmandu/d8365cb70b899901a05290d31c04909a |
Thanks! I have found them before (and their respective images), but they are limited to only a few devices:
Do you think we can use chromeos_docker28 to build Docker images for all Chromebooks devices? I'm currently having issues building for Cyan on Ubuntu.
|
Hmm. I haven't tested it on M103 in a while. Maybe invoke the script with You can also create a x86_64 subfolder, and put install.sh into there named install.sh.test to have the chromeos_docker28 use that... And then you can play with that install.sh.test script (add |
I'm working on revamping @satmandu's script over at zopolis4/chromeos-docker, and I'm also encountering the |
almost immediately after writing this, the issue ceased to exist! Once I wrap some things up, I'll upload the cyan image you were working on to my docker hub. or maybe the issue only exists some of the time, unclear |
should have what you're looking for |
Thanks, @Zopolis4 ! 馃槂 I still have the same issue as before (using @satmandu 's script). One thing changed, though: when I tested a few days ago, the image was uploaded to Docker Hub as "altoretrato / crewbase", but now it went to "altoretrato / crewbuild". The issue happens when
Then I tried your script, but it also failed:
It would be useful if the script didn't automatically removed files need to be downloaded (or built) again, like the recovery image, since simple issues (e.g., missing |
Awesome! 馃槃 Thank you so much! I'm already running it! 鉂わ笍 Now all I need to know is how can I transfer the packages from the container to the Chromebook. Any tips? |
something like so:
the built package files should appear in a |
Thanks again! And finally... what would it take for Chromebrew to support older ChromeOS versions OOTB, so |
You'd have to ask satmandu on that one, he knows the most about the way we handle glibc. I've got plans to look into this, but it may be quite some time before I get around to those. |
Hi!
It seems that, because my Chromebook (Cyan) has reached its EOL, I'm having issues with Chromebrew compiled packages requiring a more recent version of libc (see #9136). I could try building packages from source, but doing that for many large packages on a puny chromebook is a daunting task that would take forever.
But I found out @satmandu 's chromeos_docker28 script to build a Docker image using a ChromeOS recovery file. It seems that I can use it to build chromebrew packages on my desktop PC and bring them later to the Chromebook... is that correct?
I'm still in the process of building the Docker image, so I'm not even sure if I'll get that step to work at all! I don't know about the other steps as well, but I'm sure other people would be interested in trying to do the same to be able to run more chromebrew packages on their systems.
I thought about creating a wiki page about the script to help others, but it might be redundant, incomplete or even inaccurate, so first I'd like to ask if someone else have more info to contribute to such page, and if @satmandu and others in the project agree about creating such wiki page. I'd be glad to format and test that information, maybe even include a list of publicly available Docker images to make it easier for most users to just run pre-built images instead of building their own.
All your suggestions and input are welcome!
Thanks!
The text was updated successfully, but these errors were encountered: