I don't install docker locally. Instead, I install docker on the server that I SSH into via Chrome's SecureShell extension.
Having said that, starting in Chrome v68 or v69, you're able to run Docker locally on Chromebooks via Crostini VMs. Basically, you would run a command in Crosh shell which creates a minimal VM that you have full shell access on (instead of the limited Crosh shell) and Docker already installed on it. From there, you can have the local dev experience you're more used to.
Fair warning, however:
I have tried experimenting with that local development set-up on a Chromebook and it was a very poor experience for me. Chromebooks are very resource-limited devices (4GB RAM, intel m3, 64GB SSD). They're really not tailored or well-suited for local development. Running a Chrome browser with a few tabs + Spotify android app + a VM with neovim and a docker container was enough to feel sluggish. Albeit, this feature is still relatively new and the Chromium team continues to work on stabilizing and improving this.
An expression comes to mind that sums it up nicely: "Just because you can doesn't mean you should"
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't install docker locally. Instead, I install docker on the server that I SSH into via Chrome's SecureShell extension.
Having said that, starting in Chrome v68 or v69, you're able to run Docker locally on Chromebooks via Crostini VMs. Basically, you would run a command in Crosh shell which creates a minimal VM that you have full shell access on (instead of the limited Crosh shell) and Docker already installed on it. From there, you can have the local dev experience you're more used to.
Fair warning, however:
I have tried experimenting with that local development set-up on a Chromebook and it was a very poor experience for me. Chromebooks are very resource-limited devices (4GB RAM, intel m3, 64GB SSD). They're really not tailored or well-suited for local development. Running a Chrome browser with a few tabs + Spotify android app + a VM with neovim and a docker container was enough to feel sluggish. Albeit, this feature is still relatively new and the Chromium team continues to work on stabilizing and improving this.
An expression comes to mind that sums it up nicely: "Just because you can doesn't mean you should"