DeviceFarmer / stf

Control and manage Android devices from your browser.
https://devicefarmer.github.io
Other
3.41k stars 484 forks source link

Use the new dockerFile build error #130

Open s2339956 opened 3 years ago

s2339956 commented 3 years ago

After using the new dockerFile build, an error occurred during runtime stf_1 | /bin/sh: 1: stf: Permission denied Unable to construct

Starting dockerrun_rethinkdb_1 ... done
Starting dockerrun_adbd_1      ... done
Recreating dockerrun_stf_1     ... done
Attaching to dockerrun_adbd_1, dockerrun_rethinkdb_1, dockerrun_stf_1
adbd_1       | adb I 10-12 10:55:37     6     6 auth.cpp:417] adb_auth_init...
stf_1        | /bin/sh: 1: stf: Permission denied
rethinkdb_1  | Running rethinkdb 2.4.1~0buster (CLANG 7.0.1 (tags/RELEASE_701/final))...
rethinkdb_1  | Running on Linux 5.4.0-48-generic x86_64
rethinkdb_1  | Loading data from directory /data/rethinkdb_data
adbd_1       | adb I 10-12 10:55:37     6     6 auth.cpp:152] loaded new key from '/root/.android/adbkey' with fingerprint 9BB6C5623F63CB10053006DE7335A39BE64999A41891CDE4A8B03F39BD3F9135
adbd_1       | adb I 10-12 10:55:37     6     6 auth.cpp:392] adb_auth_inotify_init...
rethinkdb_1  | Listening for intracluster connections on port 29015
rethinkdb_1  | Listening for client driver connections on port 28015
rethinkdb_1  | Listening for administrative HTTP connections on port 8090
rethinkdb_1  | Listening on cluster addresses: 127.0.0.1, 172.44.0.6
rethinkdb_1  | Listening on driver addresses: 127.0.0.1, 172.44.0.6
rethinkdb_1  | Listening on http addresses: 127.0.0.1, 172.44.0.6
rethinkdb_1  | Server ready, "c5169dba248f_pzd" eebce09f-903a-4a20-9c09-b2d20719b432
issue-label-bot[bot] commented 3 years ago

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.80. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

denis99999 commented 3 years ago

@s2339956 , Please fill the bug report template, provide your docker-compose.yml file, provide additional logs if any, which Dockerfile are you talking about ?

kilabyte commented 3 years ago

was there a solution to this?