I am using macOS 10.14.6 and docker info shows me that the docker daemon is not running. How do I start the docker daemon from terminal? I have not found any information on doing so anywhere. On Linux you do something like sudo service docker stop, but this is incompatible with MacOS.

I'm migrating from Ubuntu to MacOS with my MacBook Pro (M2). I'm using ohmyzsh with the docker and docker-compose plugin. Docker has been installed with [Docker Desktop setup](https://docs.docker.com/desktop/install/mac-install/) . All works fine except the autocompletion for the container names. If I type docker start and ⮕Tab it just shows me the files of my current directory, but not the list of available containers. I'm expecting the autosuggestion to work here and show me a list of all containers which could be started. This worked fine within Ubuntu. I'd rather not run docker virtually or have to shell in to an already running container to get this functionality. Is there a trick which I could use so the macOS command line has more completion options with zsh and docker for Mac?

I am currently using a Docker container that requires squashfs to create the file system. The container fails to start up correctly and displays this in the logs: 2024-02-01 08:09:53 mount: /mnt/sqfs: unknown filesystem type 'squashfs'. To debug, I ran cat /proc/filesystems in the docker container and it did not list squashfs. I saw in [the release notes for version 4.27.0 of docker](https://docs.docker.com/desktop/release-notes/#for-all-platforms) (latest as of this question's writing): > Bug fixes and enhancements > > For all platforms: > - [...] > - Re-added kernel modules for btrfs, xfs, vfat, exfat, ntfs3, f2fs, **squashfs**, udf, 9p and autofs. I learned from [this Stack Overflow thread](https://stackoverflow.com/questions/54913641/enabling-squashfs-inside-docker) that > A Docker container cannot have a different filesystem list than their host machine so I assumed my mac was missing squashfs. I then [installed squashfs with homebrew per this thread](https://apple.stackexchange.com/q/212906/331689) but it still doesn't work. Even after restarting docker, running cat /proc/filesystems in the docker container STILL does not list squashfs. It still also shows the error above as well. How can I run a container requiring squashfs on an Intel Based Mac running Sonoma 14.3 and Docker Desktop for mac? ---------- **EDIT:** Please Note, Versions **4.27.0** and **4.27.1** of Docker for mac [have a known issue where docker crashes a few minutes after boot](https://github.com/docker/for-mac/issues/7164) . Beware if you are planning on installing these versions of docker. ---------- **EDIT 2:** Versions **4.27.2** of Docker for mac has fixed the errors in versinos **4.27.0** and **4.27.1**. After installing it, I now see squashfs listed when I run cat /proc/filesystems in the docker container. My docker container still doesn't run properly though, and I now get a different error in my docker logs: 2024-02-13 11:54:40 mount: /mnt/sqfs: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.

I run the minikube on my macos, and minikube container use the minikube network, check below:

$ docker network ls
NETWORK ID     NAME       DRIVER    SCOPE
906776761e62   bridge     bridge    local
89afa32d0810   host       host      local
b7cc12043647   minikube   bridge    local
4f7dca22f5b6   none       null      local

$ docker network inspect b7cc12043647
[
    {
        "Name": "minikube",
        "Id": "b7cc120436478e8be737a60df8fd0147e46ad09ccfbea41e564aaebff0f5ee27",
        "Created": "2021-09-28T09:57:59.40193434Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "192.168.49.0/24",
                    "Gateway": "192.168.49.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "a35d5e4b87e1bc2a747a8e1902c8bd9363d9ec1f1baf2424671d1a3a497f18ff": {
                "Name": "minikube",
                "EndpointID": "97d5f2ccc7a306f56200a0a6811f90db8e6cb0f8269762041797b2e9c25a1d63",
                "MacAddress": "02:42:c0:a8:31:02",
                "IPv4Address": "192.168.49.2/24",
                "IPv6Address": ""
            }
        },
        "Options": {
            "--icc": "",
            "--ip-masq": "",
            "com.docker.network.driver.mtu": "1500"
        },
        "Labels": {
            "created_by.minikube.sigs.k8s.io": "true"
        }
    }
]

and I also know docker on macos is running in Docker Desktop(linux VM), but now how can I use macos bridge connect to the linux VM? --- For that purpose, I have created a bridge named bridge1 on my macos.

Docker recently upgraded its license that using Docker Desktop is a paid feature. I don't use Desktop but I do use the built-in Docker Engine. The Docker > About implies they are two separate things: My question is really two: (1) if I'm not violating licensure by _only actually using_ the engine, then don't really need the rest but if not or just for grins' sake then (2) how to install docker engine without docker desktop?

I want to completely remove Docker Desktop from my macbook (M3, Sonoma) to perform a clean installation from scratch; I performed an uninstall using Appcleaner, but still I have something left on the Login Elements: I even tried to use FAF (Find Any File), but I still have not found where should be... could it be related to: \usr\share\vim\vim90\ftpplugin\dockerfile.vim \usr\share\vim\vim90\syntax\dockerfile.vim ? how can I delete those files?

I am trying to make my Mac behave similarly to a linux server, I want the Mac to start on its own when plugged in, launch a docker container for a web server without any user input. However, I don't want anybody to be able to plug a monitor into the Mac and then access the desktop UI without a password. So far I have only been able to remove the password on log in so the Mac automatically logs in and starts the web server, but then anybody can just plug a screen and use the Mac without a password. Is there a way to make it behave similarly to a linux server where it just starts on its own, runs all the backgrounds tasks but then if somebody tries to use it with a keyboard and mouse it will ask for a password ?

I had been running Docker Desktop for Mac for some months without incident. This error message cropped up, apropos of nothing, after a reboot: > "com.docker.socket" was not opened because it contains malware Anyone have an idea why, and what can be done to work around it? Simply dragging the app icon to the trash and re-installing didn't seem to help.

After installing Docker-Desktop, I noticed some weird inconsistencies when running SquirrelDisk. Lo and behold, ~/Library/Containers/com.docker.docker/Data/vms/0/Docker.raw is reported to be 1TB by the command ls -la. I'm running it on a base MacMini M4, with 256GB of hard disk so, that is phisically impossible. I have tried copying the file to an external 1TB drive which results in an error of "No space left on device." This is very inconvenient, and I would really like to understand how / why this is happening.

**Problem:** Malware warning (attached) keep popping-up on every restart and login **Question:** How do I stop the pop-ups? **Current Setup:** Installed Docker Desktop v4.37.2 and seems to start successfully. MacOS 15.2 - Apple M3 Chip. **What Happened:** - I tried to install Docker Desktop - Got the the attached warnings - Searched the issue on the web found the below links - Docker Desktop seems to be running successfully but - Pop-ups still appear on restart + login **Instructions Followed:** https://forums.docker.com/t/malware-blocked-com-docker-vmnetd-was-not-opened-because-it-contains-malware/145930/6 https://github.com/docker/for-mac/issues/7527 https://github.com/docker/for-mac/issues/7520 Existing Questions: Like: https://apple.stackexchange.com/questions/477976/com-docker-socket-was-not-opened-because-it-contains-malware These answers tackle the problem of getting Docker Desktop working but I don't think they deal with the repeating warning pop-up issue.

I'm trying to noodle out how to make this basic workflow happen in Docker Desktop for Mac, with Kaniko running inside of a Kubernetes pod: 1. Pull a base image from the local Docker context 2. Build an image on top of that with other resources 3. Publish the new image back to Docker to the local context with the goal of starting a new pod in Kubernetes that references the image that was just built, and having Kubernetes launch the pod with that new image. We're already kind of doing this in a full-blown Kubernetes cluster where Kubelet is configured to pull from an external registry via an alias of cluster.local so instead of pulling from / publishing to Docker we're talking to that registry. The Dockerfile would resemble:

ARG REGISTRY_HOST=external.registry.fqdn
FROM ${REGISTRY_HOST}/path/to/my-base-image:1.0.0

COPY ...

RUN ...

...etc...

and we publish to external.registry.fqdn/path/to/my-new-image:2.0.0. But the image name spec for the pod would be cluster.local/path/to/my-new-image:2.0.0. So in Docker Desktop we'd need to be able to configure the build argument REGISTRY_HOST so that it points to the Docker Desktop context (I think). This is primarily for being able to test the process locally, instead of having to push helm charts, etc. up to a cluster to test changes. Any suggestions on how one might go about doing something like this, perhaps with a local registry outside of Kubernetes and tweaks to kubelet to have it work like the full cluster configuration we're using would be greatly appreciated. If someone has managed to do something like this using colima and kubernetes, I will gladly take a look at that solution as well. Is there a foundation to begin this work or has someone solved this already?

On my MacBook (Sonoma 14.6.1), I've got a Python script that uses [pyaudio](https://people.csail.mit.edu/hubert/pyaudio/) (which uses portaudio) to play audio files through my speaker. The script works just fine. However, for reasons, I'd like to run the script inside of a Docker container (Ubuntu 22.04). When I run my script that way, I get

ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM sysdefault
ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM sysdefault
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.front
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround40
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround41
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround50
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround51
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_card_id returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM dmix

I'm guessing this has something to do with the container being unable to locate the audio device. Is there an option I can pass to docker run to mount the device? UPDATE: I followed the instructions given in [this SO answer](https://stackoverflow.com/a/50939994/8075540) but still received no sound output. I did, however, see some logs from the pulseaudio daemon:

AVAudioSession_MacOS.mm:2356  --> setPlayState Started Output {410C0FC2-0000-0000-0A22-010380462778, 0xa}
AVAudioSession_MacOS.mm:2379  Devices are same: =0. Previous: {()}. Current: {("410C0FC2-0000-0000-0A22-010380462778")}
AVAudioSession_MacOS.mm:981   Sent updated IOState to server: [0, 1]. BT device UIDS: {()}
AVAudioSession_MacOS.mm:2397   setPlayState Stopped Output {410C0FC2-0000-0000-0A22-010380462778, 0xa}
AVAudioSession_MacOS.mm:2379  Devices are same: =0. Previous: {("410C0FC2-0000-0000-0A22-010380462778")}. Current: {()}
AVAudioSession_MacOS.mm:981   Sent updated IOState to server: [0, 0]. BT device UIDS: {()}
AVAudioSession_MacOS.mm:2397  <-- setPlayState Server update was required.

I tried playing a .wav file from the container with paplay. The command succeeded (and took the right amount of time for the length of the .wav file) but there was no output. The corresponding pulseaudio logs were

I: [] client.c: Created 0 "Native client (TCP/IP client from 127.0.0.1:52371)"
I: [] sink-input.c: Trying to change sample spec
I: [] remap.c: Using mono to stereo remapping
I: [] speex.c: Choosing speex quality setting 1.
I: [] sink-input.c: Created input 0 "sample-1728359287.wav" on Channel_1__Channel_2 with sample spec s16le 1ch 44100Hz and channel map mono
I: [] sink-input.c:     media.format = "WAV (Microsoft)"
I: [] sink-input.c:     application.name = "paplay"
I: [] sink-input.c:     media.name = "sample-1728359287.wav"
I: [] sink-input.c:     native-protocol.peer = "TCP/IP client from 127.0.0.1:52371"
I: [] sink-input.c:     native-protocol.version = "35"
I: [] sink-input.c:     application.process.id = "40"
I: [] sink-input.c:     application.process.user = "user"
I: [] sink-input.c:     application.process.host = "02a5f943ef9c"
I: [] sink-input.c:     application.process.binary = "pacat"
I: [] sink-input.c:     application.language = "C"
I: [] sink-input.c:     application.process.machine_id = "02a5f943ef9c"
I: [] sink-input.c:     module-stream-restore.id = "sink-input-by-application-name:paplay"
I: [] protocol-native.c: Requested tlength=2000.00 ms, minreq=20.00 ms
I: [] protocol-native.c: Final latency 2250.00 ms = 1960.00 ms + 2*20.00 ms + 250.00 ms
I: [] sink-input.c: Freeing input 0 "sample-1728359287.wav"
I: [] client.c: Freed 0 "paplay"
I: [] protocol-native.c: Connection died.

I have installed via brew colima which is on the latest version available via brew **0.7.5** This is on an m2 pro chipset which should be able to support rosetta. When I try to enable rosetta support in colima and I try to start colima the following is printed. >[hostagent] Setting up Rosetta share [hostagent] Unable to configure Rosetta: failed to create a new rosetta directory share caching option: unsupported build target macOS version for 14.0 (the binary was built with __MAC_OS_X_VERSION_MAX_ALLOWED=130300; needs recompilation) Do I need to wait for a new version of Colima here?

I am looking for a way to create a new mount point for a directory similar to the mount --bind command in Linux. In Linux, mount --bind creates a so-called bind mount which takes an existing directory tree and replicates it under a different point. The directories and files in the bind mount *are the same as the original*. Any modification on one side is immediately reflected on the other side, since the two views show the same data. A symlink won't work because I'm working with Docker and Docker disallows symlinks when building images from a Dockerfile. I prefer solutions that work on macOS Sonoma.

Using this version of docker, The swap memory in docker desktop is limited to 4GB. >On windows, this default value could be doubled by specifying **"SwapMiB": 8192** in a settings file located at %userprofile%\AppData\Roaming\Docker\settings.json > This file is read at startup, so after making changes, restart the app. How do I increase this limit on the macOS version of docker desktop app?

I have an MacBook Air (10.14.6) and the folder ~/Library/Containers/com.docker.docker/ contains 64 GB of data!! How to clean up this folder?

After installing *Docker Desktop* app version 4.25 on my MacBook Pro running macOS Sonoma, I was prompted to install Rosetta 2 . I verified that I had indeed downloaded the version of Docker Desktop for Apple Silicon, not Intel. What part of Docker Desktop requires Rosetta? I suppose it is not really a problem, but I am curious.

I installed the docker-engine in macOS from https://docs.docker.com/desktop/install/mac-install/ which says, > The Docker Desktop installation includes Docker Engine, Docker CLI client, *Docker Compose*, Notary, Kubernetes, and Credential Helper. But when using docker-compose, I'm getting: docker: 'compose' is not a docker command. What's wrong please? Full log:

$ /Applications/Docker.app/Contents/Resources/bin/docker -v
Docker version 24.0.7, build afdd53b

$ /Applications/Docker.app/Contents/Resources/bin/docker-compose -v
docker: 'compose' is not a docker command.
See 'docker --help'

$ sw_vers
ProductName:            macOS
ProductVersion:         14.2.1
BuildVersion:           23C71

**UPDATE:** It's an *invalid* question -- the problem is else where:

$ type docker
docker is /usr/local/bin/docker

$ ls -l /usr/local/bin/docker*
ls: cannot read symbolic link '/usr/local/bin/docker': Permission denied
ls: cannot read symbolic link '/usr/local/bin/docker-credential-desktop': Permission denied
ls: cannot read symbolic link '/usr/local/bin/docker-credential-ecr-login': Permission denied
ls: cannot read symbolic link '/usr/local/bin/docker-credential-osxkeychain': Permission denied
ls: cannot read symbolic link '/usr/local/bin/docker-index': Permission denied
lrwxr-x--x 1 root wheel 54 Feb  2 13:46 /usr/local/bin/docker
lrwxr-x--x 1 root wheel 73 Feb  2 13:46 /usr/local/bin/docker-credential-desktop
lrwxr-x--x 1 root wheel 75 Feb  2 13:46 /usr/local/bin/docker-credential-ecr-login
lrwxr-x--x 1 root wheel 77 Feb  2 13:46 /usr/local/bin/docker-credential-osxkeychain
lrwxr-x--x 1 root wheel 60 Feb  2 13:46 /usr/local/bin/docker-index

I.e., I symlink docker apps into /usr/local/bin/ but somehow they failed:

$ sudo rm /usr/local/bin/docker*

$ ls -l /usr/local/bin/docker*
ls: cannot access '/usr/local/bin/docker*': No such file or directory

$ sudo ln -s /Applications/Docker.app/Contents/Resources/bin/docker /usr/local/bin

$ ls -l /usr/local/bin/docker*
ls: cannot read symbolic link '/usr/local/bin/docker': Permission denied
lrwxr-x--x 1 root wheel 54 Feb  3 15:09 /usr/local/bin/docker

However, I don't know how, but after I tried it several times, it is suddenly working:

$ ls -l /usr/local/bin/docker*
lrwxr-xr-x 1 root wheel 54 Feb  3 15:15 /usr/local/bin/docker -> /Applications/Docker.app/Contents/Resources/bin/docker
lrwxr-xr-x 1 root wheel 62 Feb  3 15:15 /usr/local/bin/docker-compose -> /Applications/Docker.app/Contents/Resources/bin/docker-compose
lrwxr-xr-x 1 root wheel 73 Feb  3 15:15 /usr/local/bin/docker-credential-desktop -> /Applications/Docker.app/Contents/Resources/bin/docker-credential-desktop
lrwxr-xr-x 1 root wheel 75 Feb  3 15:15 /usr/local/bin/docker-credential-ecr-login -> /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login
lrwxr-xr-x 1 root wheel 77 Feb  3 15:15 /usr/local/bin/docker-credential-osxkeychain -> /Applications/Docker.app/Contents/Resources/bin/docker-credential-osxkeychain
lrwxr-xr-x 1 root wheel 60 Feb  3 15:15 /usr/local/bin/docker-index -> /Applications/Docker.app/Contents/Resources/bin/docker-index

$ docker-compose -v
Docker Compose version v2.23.3-desktop.2

I don't know why it didn't work and, I don't know how it works again, so I'm accepting whatever answer I have and move on.

Hopefully I describe this in the way it can help me. Is it possible for me to host a drive live on a website of mine, in which users anywhere, (not just my network), can access to watch/listen/play and download stuff from? Similarly to Snap2HTML, the application takes a snapshot of a folder's structure, and pastes it on a HTML file you can use for a website. My desired result is just like this, but I can use it on MacOS systems, since Snap2HTML is Windows only. Being that, I did indeed test it on CrossOver, which it built the .html just fine, but I cannot redownload the files from where the .html was appointed to. Essentially, I want to host my own file hosting service, apart from anyone else uploading anything to the drive. Anyone who visits my site, can download those files I put into the drive, that looks like an Index of that drive, similarly to the Raspberry Pi OS' previous image UX. If anything of the similar is possible and available for Mac, please let me know. Thanks in advance!

On my MacBook Pro I have 8 performance cores with 2 efficiency cores. So I have 10 cores total. In my Docker Desktop configuration I can choose how many cores are allocated for use of Docker. Is there guidance on how many cores I should give to it? I do builds in the containers, so being able to pass higher -j values is helpful. I currently have Docker configured for 8 of my 10 cores. 10 would probably be better for my dev work, but is assigning all cores not advisable? I can't find guidance or heuristics on choosing this on a Mac host.