mirror of
https://github.com/budtmo/docker-android.git
synced 2026-04-25 12:15:52 +03:00
[GH-ISSUE #9] docker-appium as base image #6
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/docker-android#6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @budtmo on GitHub (May 24, 2017).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/9
Using docker-appium as base image https://github.com/appium/appium-docker-android/tree/master/Appium. It will be implemented after release of new version of docker-appium.
@budtmo commented on GitHub (May 26, 2017):
delete libgconf-2-4 from docker-android as soon as docker-appium is used as a base image. see: https://github.com/appium/appium-docker-android/pull/38
@andrcuns commented on GitHub (May 26, 2017):
Me and my chromedriver issues again :D One thing to consider, since docker-appium uses latest appium version, it comes with a pretty recent, most likely latest chromedriver versions which causes issues when running against even latest 7.1.1 android image since by default it has chrome 53 if I'm not mistaken which is a bit too old for latest chromedriver. One option would be add ability with to start appium with custom chromedriver executable which is achieved with
--chromedriver-executableoption.@budtmo commented on GitHub (May 26, 2017):
thank you for this info @andrcuns!
@andrcuns commented on GitHub (Jun 6, 2017):
Added PR #12 to help with potential problem described above.
@budtmo commented on GitHub (Jun 14, 2017):
Done on release 0.7