dockerfiles

Worth mentioning Jess Frazelle was running desktop applications in docker a while ago. Not a full desktop, but also quicker to rebuild individual apps. https://blog.jessfraz.com/post/docker-containers-on-the-desk... https://github.com/jessfraz/dockerfiles

DB data can be stored in volume and persisted. There are a lot of dockerfile / compose examples on github. * https://github.com/docker/awesome-compose * https://github.com/jessfraz/dockerfiles

Some of my day-to-day software. After knowing that saved Chrome passwords and cookies in Linux are not protected against malicious dependencies in our development environment or other apps in our system, I decided to run my core apps in Docker containers, where their data is not accessible without sudo, and a personal understanding of where stuff is being saved. These docker containers are also an improved version of https://github.com/jessfraz/dockerfiles/ Contrary to the project above, docker-workspaces runs Chrome in a sandbox, encrypts keys with the help of an also dockerized gnome-keychain, and works in tandem with pulseaudio, so you can use wired headphones (i still need to add some dependencies for it to work with bluetooth headphones).

jessfraz maintains quite a collection of Dockerfiles you can borrow: https://github.com/jessfraz/dockerfiles

The blog post links to Jessie Frazelle's GitHub repo [0]. Jessie also has a blog post about this [1] from back in 2015. If you prefer video format, Jessie also has a talk at DockerCon SF 2015 [2]. [0] https://github.com/jessfraz/dockerfiles [1] https://blog.jessfraz.com/post/docker-containers-on-the-desk... [2] https://www.youtube.com/watch?v=cYsVvV1aVss

On unix systems that still use a 1970s permissions model, this is true, but it's been fixed on mobile devices for ages, and macOS desktops for over a year (this bug notwithstanding). Ransomware (enabled by bitcoin payments to anonymous recipients) really changed the game on desktop in the last few years. Apple stepped up, but there's crickets on the matter in Windows- and Linux-land, aside from the people who have been containerizing their desktop apps[1]. [1]: https://github.com/jessfraz/dockerfiles/blob/master/chrome/s...

Hi, I'm the author. Thanks for taking a look. This is basically a tool to help manage a "Dockerfile" repo (along the lines of https://github.com/jessfraz/dockerfiles), where you build any tools you want into images that you control. This can be really useful for personal use or within a company. Why build tools into Docker images? Love it or hate it, there are many senses in which Docker is currently the best medium that we have for distributing and running dev tools. Here's an article making that argument: https://jonathan.bergknoff.com/journal/run-more-stuff-in-doc....

jessfraz has a great collection of Dockerfiles for various applications: https://github.com/jessfraz/dockerfiles x11docker provides tooling: https://github.com/mviereck/x11docker

It's interesting to see the complaint about containers starting too slowly. I haven't seen much discussion about it before this article and this comment thread, but it's one of my biggest pain points with Docker. I know we can save some time by skipping some namespaces (e.g. `--net host`) but I've still never been able to get satisfyingly fast container execution in that way. (e.g. `time echo` -> 0.000s, `time docker run --rm alpine echo` -> 1.3s; come to think of it, this is even slower than it used to be) Still, Docker is the best method that I've seen for distributing software, especially cross-platform. Not just for shipping a containerized web app to production, but also running dev tools (e.g. linters, compilers) and other desktop and CLI applications. I know some people run lots of stuff in containers (https://github.com/jessfraz/d

Some people run Chrome in a container: https://github.com/jessfraz/dockerfiles/blob/master/chrome/s... It could be configured to run in a totally clean container to keep the browser reasonably isolated from the host system. Of course, the truly harcore can use Qubes OS and spawn a disposable VM to browse the web from: https://www.qubes-os.org/doc/disposablevm/

I'm curious what about running a container like this is hard as you've implied? Take for example all the great work Jessie Frazelle has done containerizing her desktop and apps (https://github.com/jessfraz/dockerfiles). Or the folks behind LinuxServer.IO. If you already have a container runtime on your system running this, as suggested, is a one-liner.

I got a new MacBook Pro from work a couple of months ago, and decided to try a scaled back version of this. You can’t reasonably run graphical apps in Docker on MacOS, but most of the CLI tools that I would install via HomeBrew can be run in Docker. I took the same approach that Jess did, and set up a a shell alias for these commands. That way I run the command the way I would normally run it from Terminal.app, but the app isn’t installed at all on my host. To be clear: I have no real reason to do this, other than to just see how it works. It’s nice to know that if I got a new machine tomorrow, all of the CLI stuff I need is defined in some Dockerfiles and bash aliases, and could be reinstalled pretty quickly. There are other ways to do that, but it’s a fun experiment. In practice, there’s really very little noticeable overhead to running

I generally tend to disagree with the "Dockerize Everything" crowd, but process isolation is one of the cases where Docker shines. And while it won't magically protect your identity, it's a fast way of having a browser start from a clean slate on each boot. There's a lot of discussion on privacy-related Chrome issues recently on HN. Chrome/Chromium are excellent pieces of software, that are crucial to some of our workflow. If you ever need to run something like this, Jessie Frazelle's GitHub [1] has an excellent, evolving collection of Dockerfiles, for a wide array of software, that can be used as a cheatsheet. [1] https://github.com/jessfraz/dockerfiles

https://github.com/jessfraz/dockerfiles/blob/master/chrome/s... https://github.com/jessfraz/dockerfiles/blob/master/firefox/...

Maybe you already saw this: https://blog.jessfraz.com/post/docker-containers-on-the-desk... It's pretty dated, but the state of containers has only improved since 2015, and this was usable for Google Hangouts (video) and YouTube all the way back then. https://hub.docker.com/r/jess/chrome/ ^ This got a push less than 24 hours ago https://github.com/jessfraz/dockerfiles/blob/master/chrome/s... ^ This is the Dockerfile, in a repo full of Dockerfiles for other things you might have had trouble putting into a container. I tried this myself and had problems because (I think) I was on a very old LTS/stable distro with a necessity to use pretty old Docker release. This person is a maintainer on the Docker core team, so is most definitely tracking newest releases. I use Chrome in a headless setup with Kubernetes and Docker (Jenkins with kubernete