Vega Virtual Device Not Working in Docker Container

[William_Roberts]

Before you continue

---

Before submitting a bug report, please review our troubleshooting documentation at Troubleshoot Issues | Vega Troubleshooting

If you still want to file a bug report, please make sure to fill in all the details below and provide the necessary information.

NOTE: PLEASE ONLY REPORT A SINGLE BUG USING THIS TEMPLATE.
If you’re experiencing multiple issues, please file a separate report for each.

---

Bug Description

---

1. Summary

Provide a brief description of the bug in the SDK and its impact on app functionality.

The bug is that the Vega (Kepler) Virtual Device will not start when running in a Docker container. My team and I created a Dockerfile based on continuous-integration example-dockerfile and when running on a macOS or Linux host the command % kepler device simulator start gives the following:

Creating default instance.

Instance path: /kepler/0.21.5245/kvd/instances/9629e580-b181-4bc4-8e59-78ca71621b2c

Launching default instance.

Waiting for virtual device to boot.

Launch process complete.

Launch failed with error code 0.

Cleaning up. Killing virtual device process with pid 116.

Kepler operation FAILED due to an irrecoverable error: kill ESRCH

Additional logs can be found at /root/.kepler/logs

Note that I’ve tried running this also with the --no-gui flag, but it basically does the same thing.

The logs in /root/.kepler/logs do not show any relevant errors as far as I can tell either.

App Name: n/a

Bug Severity
Select one that applies

• Impacts operation of app
• Blocks current development
• Improvement suggestion
• Issue with documentation (If selected, please share the doc link and describe the issue)
• Other

2. Steps to Reproduce

1. Create a dockerfile based on the documentation (see link in summary, I can’t post two links in this ticket apparently).
2. Open the container in a shell and run kepler device simulator start -t 600 (or with whatever relevant flags
3. Notice that the simulator fails to boot properly.
   1. I have noticed that occasionally it may finish booting, but then when I try to install my application, e.g. % kepler device install-app –device emulator-5554 -p path/to/app.vpkg it fails here too.

3. Observed Behavior

As mentioned above in #2, the simulator fails to boot properly and does not give any relevant information in the log files. If it does boot (few and far between) it is then unable to install a vpkg.

4. Expected Behavior

The simulator boots within the expected time, and the application is able to be installed on the simulator in the Docker container.

4.a Possible Root Cause & Temporary Workaround

I’ve tried with multiple SDK versions, multiple hosts (ubuntu and macOS docker hosts) and with multiple --no-gui and -t 600 flags.

5. Logs or crash report

I did not see anything relevant in the log files, which is also another aspect of this bug.

6. Environment

Please fill out the fields related to your bug below:

• SDK Version: 0.21.5245 and 0.21.4677 both gave me this issue.

• App State: N/A

• OS Information
  The host running docker is Ubuntu 22.04.5 LTS, and also the dockerfile is FROM ubuntu:22.04 - same as the Amazon doc’s example Dockerfile.

7. Example Code Snippet / Screenshots / Screengrabs

The rest of these questions are all N/A

---

Playback Issues

---

If this is a playback issue, please provide your content URL, any pre-conditions (like geo-location), and let us know if it’s x86 or arm7.

<!-- Describe your playback issue if applicable -->

Please share the following details in addition:_

• Player SDK: [Bitmovin, Shaka, ...]
• Player SDK Version: [e.g. 1.23]
  • Audio Codecs: [AAC, ...]
  • Video Codecs: [h.264, mp4]
  • Manifest Types: [m3u8, dash, etc ..]

Q: If applicable, please provide your media/content url
If this is created dynamically, tokenized, etc please provide a way for us to access it

[N/A or Content / Media Url for testing]

Q: Are there any special headers required to reproduce the issue you are facing?

[N/A or Insert Headers]

Additionally please provide the following if possible
Provide Screenshots / Screengrabs / Logs. Please include as much information as you can that will help debug.

<!-- Answer here if applicable --> 

---

Additional Context

---

Any Additional Context you would like to provide?
Add any other relevant information, such as recent updates to the SDK, dependencies, or device OS that may affect the bug.

<!-- Answer here if applicable  --> 

[amen]

Hi @William_Roberts,

Welcome to Amazon Developer Community!!

Thank you for the detailed bug report on the Vega Virtual Device Docker container issue.

Our team is investigating this issue and will provide an update as soon as we have more information.

Thanks for helping us improve the Vega platform.

Warm regards,
Aishwarya

[Monica]

Hi,

At the moment, Vega Virtual Device does not support running in Docker or in other nested-virtualization environments. This type of setup makes the VVD very slow and unstable, which matches the behaviour you are seeing.

Our recommendation is to run the simulator directly on the host OS.

Kind regards,
Monica