-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provide debug option for the mcloud-device container #135
Comments
To check this enhancement you need to change Dockerfile variables before build: ENV DEBUG=true
ENV DEBUG_TIMEOUT=3600
ENV VERBOSE=true or run an already built container with docker run -d --env DEBUG=true --env VERBOSE=true ... IMAGE [COMMAND] [ARG...] after that you need to broke some code to provoke container to exit (in usual situation) and check that container has not exited. Also you need to check logs for verbose output. |
Debug and Verbose mods are present, but we catch log issue /opt/debug.sh: line 12: 3600: command not found log:
|
fixed |
Verified. |
in case of any problem we do have device containers in restarting state:
let's introduce new DEBUG mode which allow us to stay at the end so user can bash into the container and test all kind of infrastructure settings. Ideally it should be organized via start command argument.
if
DEBUG=true
we should prohibit exit and restart and stay as is...The same should be implemented for appium container
The text was updated successfully, but these errors were encountered: