Context If my docker app were to require a kernel module, I’d have to build my module on the same environment as the base VM that the Docker Mac Beta runs on. Currently the base VM is Alpine linux Kernel version 4.4.6 and I don’t have a choice to pick another distro. I’d like to have that choice.
I’d like to be able to run specific versions of libs (gcc, libc, openssl…) when I build my kernel modules for my app (hobby app: trying to run my raspberry pi based coffee machine on docker!). With docker-machine (running distro of my choice - b2d (debian, tce), ubuntu, centos), I could do this easily. I expect to do the same w “Docker mac”
Turns out, Alpine package manager has limited set of packages forcing devs to build these from source. This can be tedious and cause a significant degradation in user experience for folks moving to Docker to build their apps.
- While this can easily be done using a linux box, I use Mac to do my development
- I think Alpine linux is awesome to run your final app (even in prod). As a dev I’d rather not run it as my base environment.
- Mac for beta is pretty nifty, certainly consumes less resources, results in longer battery life. I get the trade-off between all of that goodness and the slimmed down version of the distro running underneath. I’d just like to have the choice when I start doing kernel work.
(This is not a bug but a feature request)
Steps to reproduce the behavior
- Just try to build any kernel driver (that requires gcc-4.9) in an alpine container on top of docker mac beta