New issue
Advanced search Search tips

Issue 622086 link

Starred by 8 users

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

API request: chrome.lxc

Reported by kenny.st...@gmail.com, Jun 21 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8481.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2773.0 Safari/537.36
Platform: 8481.0.0 (Official Build) canary-channel kip

Steps to reproduce the problem:
N/A (feature request)

What is the expected behavior?
N/A (feature request)

What went wrong?
N/A (feature request)

Did this work before? N/A 

Chrome version: 53.0.2773.0  Channel: canary
OS Version: 8481.0.0
Flash Version: Shockwave Flash 22.0 r0

Opening up LXC to third parties to allow pieces of software like Android Studio (especially important) to run inside their own Linux containers is definitely something to consider here.
 
Sorry I wasn't more specific; tried to be before only to get a 500 Internal Server Error: This would be a JavaScript API containing wrappers for the lxc-create, etc. commands.

Comment 2 Deleted

Comment 3 Deleted

Attaching API spec as PDF and deleting link to Google document due to faster load in the PDF case
chromedotlxc.pdf
27.4 KB Download
Components: Platform>ARC
Status: Untriaged (was: Unconfirmed)
Someone please mark this as a Pri-1 issue so that it gets more attention from top devs
Also, @dhadd...: Might want to also mark Issue 625333 with "Platform>ARC" since it's also an ARC issue.
Still no triage after 8 months. Needs attention!
Components: Platform>Apps>ARC

Sign in to add a comment