Docker compatibility / switching back to regular console
See original GitHub issueI’m curious as to the path I can take to implement this…
- I’d like to be able to run the UI in a docker container - specifically on Kubernetes, being able to attach to a pod and use a UI. The app runs, but I get “container did not allocate a TTY” when connecting, and the UI doesn’t display correctly. Is there any big reason for this?
- I’d like to be able to switch on/off the UI. Looking at the drivers, it looks like the input is handled with a
while(true)
in aTask.Run
, so it seems infinite? Do I have that right?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Switching users inside Docker image to a non-root user
With docker exec , use --user to specify which user account the interactive terminal will use (the container should be running and the...
Read more >Change Docker Desktop settings on Windows
Open Docker Desktop dashboard at startup. Select to automatically open the dashboard when starting Docker Desktop. Use Enhanced Container Isolation. Select to ...
Read more >Migrate to Compose V2
This change lets you use all of the shared flags on the root docker command. ... In Compose V2, the global --compatibility flag...
Read more >Change Docker Desktop settings on Mac
By default, Docker Desktop is set to use 2 GB of your host's memory. To increase the RAM, set this to a higher...
Read more >docker run
Use docker ps -a to view a list of all containers, including those that are stopped. For example uses of this command, refer...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here is a simple example
They are infinite loops handled by
ManualResetEventSlim
objects. WhenApplication.Shutdown
is called the driver is stopped ending the application.