If you want to add a package to this, open a pull request against whalebrew-packages. We maintain a set of packages which are known to follow these requirements under the whalebrew organization on GitHub and Docker Hub. If it fails, the uninstallation process fails, but the package is not uninstalled This hook is called after a package is uninstalled. If it fails, the whole uninstallation process fails This hook is called before uninstalling a package. If it fails, the installation process fails, but the package is not uninstalled This hook is called after a package is installed. If it fails, the whole installation process fails This hook is called before installing a package. Those hooks must be executable files located in $ Whalebrew makes those things work with Docker, too. Docker works well for packaging up development environments, but there are lots of tools that arent tied to a particular project: awscli for managing your AWS account, ffmpeg for converting video, wget for downloading files, and so on. To do so, whalebrew will call git-like hooks when handling installation/uninstallation of a package. Its like Homebrew, but with Docker images. In some cases, you might want to execute custom actions, like checking the integrity of the image or adding the whalebrew scripts to your whalebrew repository. LABEL io._dir '$PWD'Īt runtime, it will bind your working directory into the container at the same path and set it as the working directory.
Next, you can install whalebrew via Homebrew on macOS and Linux: The easiest way to do this on macOS is by installing Docker for Mac.
Whalebrew packages work on any modern version of macOS, Linux, and Windows (coming soon).įirst, install Docker. Package managers tend to be very closely tied to the system they are running on. For example, a Python app that requires C libraries, specific package versions, and other CLI tools that you don't want to clutter up your machine with.
Some of the instructions about docker installation on Mac OS use the latter code that installs Docker as an Application, which you can see a good explanation. Whalebrew can run almost any CLI tool, but it isn't for everything (e.g. Docker installation via Homebrew brew install docker docker -version Docker version 18.09.5, build e8ff056 Note that brew install docker and brew cask install docker is different. □ Installed whalebrew/whalesay to /usr/local/bin/whalesay Status: Downloaded newer image for whalebrew/whalesay:latest To run your own virtual machine you can look into using a hypervisor like Virtualbox to run your own linux virtual machine on your mac.Unable to find image 'whalebrew/whalesay' locallyĭigest: sha256:5f3a2782b400b2b23774709e0685d65b4493c6cbdb62fff6bbbd2a6bd393845b For example docker bind mounts are a core concept in docker, however to get them to work on your Mac, docker desktop must also take responsibility to bridge the gap between MacOS and the Linux virtual machine. But be aware that you may be using some features of docker desktop that you didn't realise were "features". That may be the case, I don't know your needs.
I don't need any of the features that are exclusive to Docker Desktop® Since these two features are the core of container technology you're highly unlikely to find other non-docker solutions (including Podman) will work either. This is because Docker is a wrapper for namespaces and cgroups which are both Linux concepts with no implementation in the MacOS kernel. Is there a way to install the linux version of docker in macOS? This explains why docker desktop has the concept of allocated resources including a "disk image size" which have nothing to do with docker engine itself. I have docker desktop running on my Macbook and to the best of my knowledge this is achieved by docker desktop creating a Linux virtual machine and running the Docker engine in that. As far as I'm aware docker is functionally incompatible with MacOS.