Hey CloudReady fans!
In an effort to help facilitate the kind of experimentation and exploration that has historically helped fuel progress in the world of Linux, we've included Docker in 64bit builds of CloudReady: Home Edition v63.
We're not going to try to educate users on how to use Docker for now. It is our hope that both internally at Neverware and across our growing population of CloudReady: Home Edition users, those who already know how to use Docker, and those who want to learn, will take it upon themselves to try things out and report back.
If you want to try using Docker on CloudReady:
- Make sure you're on v63 or higher of the 64bit CloudReady: Home Edition
- As of Feb. 27th 2018, you need to be on the Dev/Beta release channel to update to v63
- Log in
- Press ctl+alt+t to open a terminal
- Type in "shell" and hit enter
- Confirm that the yellow "crosh" prompt is now a green "chronos@localhost" prompt
- Run
sudo start docker
(the need to run this command is new in v66.4+) - Run the command
docker --version
you should see:
- If you see that output - congrats! It's working.
- Now you can run
docker -h
to get a long list of the commands and syntax docker expects.
From here, you're on your own to find uses for it with CloudReady.
If you want to learn about using Docker:
Docker's website has a great guide- you can start at that link (skip the part about installing it, as it is built-in).
If you want Docker to run automatically on CloudReady:
Starting in v66.4, Docker is disabled by default to prevent conflicts with other network setups.
If you are using Docker regularly and would like CloudReady to automatically start it when your device starts, there's a simple way to configure that:
1) Log in
2) Press ctl+alt+t to open a terminal
3) Type in "shell" and hit enter
4) Confirm that the yellow "crosh" prompt is now a green "chronos@localhost" prompt
5) Run this command:
sudo touch /home/chronos/.enable_docker_service
Now Docker will start after each boot. You cen remove that same file to undo this change
If you want to talk about how you're using Docker on CloudReady:
Post detailed instructions, links to and descriptions of useful containers you're using, or anything else relevant to Docker in our new Docker section of the Forums!
Comments
20 comments
I'm kinda new to Linux so what's the use of this feature?
http://bfy.tw/H0d5
Thanks. Not a feature for me but for others yeah
This looks like a very interesting.
I think this is going to keep me busy for days!
Forrest, it looks like when you guys added Flatpak and renamed the forum it broke your link above, the new link appears to be https://neverware.zendesk.com/hc/en-us/community/topics/360000017388-Flatpaks-Docker-VMs-etc
Thanks dragon!
I have recently replaced Mac OS Mojave on my 2015 MacBook Air with CloudReady and I'm determined to make the switch permanent! One key item was the ability to spin up Docker containers, which this support article covers off on. However, I also needed to have 'docker-compose' to spin up my development environment.
After a lot of searching I found the solution that works and wanted to post the link/details here in case someone else was looking for a solution.
The approach that worked for me was to Install Docker Compose as a Container.
After following those steps, I was able to spin up my dev environment with one command.
Hopefully this helps someone else out who may be looking.
P.S. To the CloudReady team: THANKS FOR THE GREAT WORK! Crazy that Apple's native OS will not support more than 1 external display (only DP 1.1) even though the hardware supports DP 1.2. CloudReady allows me to have two external displays with an extended desktop. Thanks again!
Thrilled to hear you're using Docker on CloudReady, and that it gives you more on the hardware that you have. That's why we make it so, cheers!
Has anybody tried Onlyoffice-document-server as a docker? Possibly together with Nextcloud, or by itself?
I'd like Onlyoffice to try:
1. Using onlyoffice in the browser. Whether connected or not.
2. Using the logins to dropbox/box/webdav etc. witthout having to store the credentials online in personal.onlyoffice.com.
3. Possibly used in conjunction with a locally installed Onlyofice-desktopeditors to store encrypted externally?
Any other experiences?
Thanks.
J.
Has anybody tried nextcloud or nextcloud+onlyoffice in docker on Cloudready-docker?
I would be interested in:
1.. Using access to a local nextcloud that can store in remote webdav/nextcloud/box/gdrive that is always encrypted.
2. Possibly using local onlyoffice with added blockchain encryption to remote as well.
3. Running nextcloud apps like their epub-reader, dicom medical photoviewer etc.
Thanks,
J.
Forrest,
Last time I tried Docker was a few months back, and it had problems.
I am happy to say I was able to run it successfully now on version 72.4.61. I made a sample image, ran it and everything worked flawlessly. I followed the initial learn/use documentation at Docker that Forrest had posted at the beginning of this thread. Thank you!
That's awesome!
Thanks for the feedback Nero - appreciate you taking the time to let us know it got better.
If you ever end up doing something interesting with docker on CR please share the details in a new post - I always want to lean more about how folks find that feature useful.
One can create images fine. But I cannot login to Docker to tag images or to push an image out there. The problem is the read only file system.
When using the docker login command (once you have created a login account at docker),
the login succeeds (if the login had failed I will give another error msg), but then it fails when the credentials cannot be saved:
Anybody knows a way to get around this?
Another problem. The stateful_partition is almost used up by docker. How does one increase the size of the stateful_partition?
docker is using up almost half of the stateful_partition. I have created only about 200MB of images.
At this point until docker login can be made to work, this no space is a moot problem.
Is there a way to delete the files and directories under docker that I created while playing with it. Suggestions?
You can remount as read write:
and it should prevent the first issue.
As for the size of the stateful partition - if you install from USB to a disk, it'll expand to fill all available space, but on an installer USB the space is limited.
As for deleting files and directories from Docker, I would guess that normal Docker commands/controls would do the trick.
1. So far, I didn't have to compromise the security my the root rw. I would prefer to keep it that way. Hopefully the developers would eventually figure out how to store the credentials in some normal place like the rest of the applications do.
2. Yes I am running from usb. I do not have enough space on my windows lap top to install cloudready there.
I will try the various docker commands. So far removing most of the images I build did not reduce it. But I will keep trying...
Thanks for responding.
Nero,
There aren't really other applications - the browser is first-part built by Neverware and has special privileges, and there are virtually no other executables running outside the browser/browser's control besides Docker and Flatpaks. It's sort of an all-or-nothing security model, and Docker doesn't fit in perfectly at this point.
You can alwasy make a new USB installer to start fresh if there's storage space loss building up over time. That'd be my backup-plan suggestion.
If I increase size of partition 16 by, say 2GB, will I get that increase in the stateful_partition space automatically? Perhaps at the build?
I think I can simply do,
stop docker
rm -rf /mnt/jstateful_partitiion/docker
to remove all of docker's store.
After
start docker
all initial files are created there taking about 245MB.
Glad you found a way to clear Docker's stateful content.
I believe that if you can expand partition 16 then the OS will automatically recognize it as available.
Please sign in to leave a comment.