Got it, let's break down how to get your Docker container talking to your local Mac's Android emulator (emulator-5554). The root issue is Docker's default network isolation—your container can't see the local adb daemon or emulator unless we explicitly bridge those resources.

Prerequisite: Match ADB Versions First #

First things first: your local Mac's adb and the adb inside your container must be the same version. Mismatched versions will cause connection failures (you might see devices listed as "offline" or not at all).

• Check local adb version:

  adb version
  

• Check container adb version (run this inside your container):

  adb version
  

If they don't match, either update your local Android SDK's adb, or install the matching adb version inside your container (using your package manager, e.g., apt install adb=X.X.X for Debian/Ubuntu-based containers).

Option 1: Share the ADB Unix Socket (Recommended, Most Stable) #

Mac's adb daemon uses a Unix socket to communicate with devices. We can mount this socket directly into the container so it uses your local adb instance instead of its own.

1. First, confirm the path of your local adb socket. On most Mac setups, it's either:

   • /var/run/adb.sock
   • Or $HOME/.android/adb_socket (if you've customized adb settings)

   You can verify with this command:

   lsof -i :5037 | grep adb
   

   Look for the "NAME" column—it'll show the socket path.

2. Start your container with a volume mount for the socket, plus --privileged to ensure the container has access to the socket:

   # Replace /path/to/local/adb.sock with your actual socket path
   docker run -v /path/to/local/adb.sock:/var/run/adb.sock --privileged your-container-image
   

3. Now inside the container, run:

   adb devices
   

   You should see emulator-5554 device listed, same as your local Mac.

Option 2: Connect via TCP to Local ADB Daemon #

If you prefer not to mount the socket, you can configure the container's adb to connect to your local Mac's adb daemon over TCP.

1. Stop any running adb daemon on your Mac, then restart it to listen on all network interfaces:

   adb kill-server
   adb -a -P 5037 nodaemon server
   

   Keep this terminal window open—this command runs the adb daemon in the foreground.

2. Start your container, setting the ADB_SERVER_SOCKET environment variable to point to your local Mac (Docker on Mac uses host.docker.internal to reference the host machine):

   docker run -e ADB_SERVER_SOCKET=tcp:host.docker.internal:5037 your-container-image
   

3. Inside the container, run adb devices—you'll see your emulator listed.

Option 3: Directly Connect to the Emulator's TCP Port #

You can also connect the container directly to the emulator's 5554 port:

1. On your local Mac, enable TCP connections for the emulator:

   adb tcpip 5554
   

2. Start your container with port mapping, then connect to the emulator from inside:

   # Start container with port mapping
   docker run -p 5554:5554 your-container-image
   
   # Inside the container, connect to the emulator
   adb connect host.docker.internal:5554
   

   Then run adb devices to confirm the connection.

Troubleshooting Tips #

• If you get "permission denied" errors with the socket mount, make sure the container's user has read/write access to the mounted socket. You can add --user $(id -u):$(id -g) to the docker run command to match your local user's permissions.
• Double-check that your local emulator is running and visible via adb devices before trying to connect from the container.
• If devices show up as "offline", 9 times out of 10 it's an adb version mismatch—go back to the prerequisite step.

内容的提问来源于stack exchange，提问作者user2274204