appium / appium/appium-docker-android
Appium-docker-android with Dockremap
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 672
- Forks
- 239
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 5
Description
Hello,
I'm currently using an Appium container, but for security reasons I had to set up Dockremap on the host machine. This security configuration no longer allows the use of --privileged. To get around this problem, I installed ADB on the host machine and added the following parameters to the container:
- ANDROID_ADB_SERVER_ADDRESS
- ANDROID_ADB_SERVER_PORT
- REMOTE_ADB
This allows me to properly detect my devices in the container. However, in tests, I always encounter the same problem in the appium container logs :
/adb -P 5037 -s device forward tcp:8200 tcp:6790' exited with code 1'; Command output: adb: error: more than one device/emulator
Do you have a solution to this problem, or have you already implemented Dockremap with an Appium container?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Appium container configuration and the host ADB setup, especially ANDROID_ADB_SERVER_ADDRESS, ANDROID_ADB_SERVER_PORT, and REMOTE_ADB. Reproduce the /adb -P 5037 -s device forward failure with Dockremap enabled and determine whether the container can select a single device without --privileged; done means documenting a confirmed configuration or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, docker, shell
- Domain
- devops, mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100