-
Notifications
You must be signed in to change notification settings - Fork 319
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
"tilt up" from hello-world leads to "libva error" #5732
Comments
😱 Sorry to hear about that @yogeek . Can you run
from the command-line? What happens? That message usually means you have your default browser badly misconfigured on linux. You can also open the tilt web ui directly at http://localhost:10350/ |
@nicks thanks for your help.
the problem, is that, with tilt, the browser also opens automatically event with the error message, but the page http://localhost:10350 displays so finally, I think i have 2 issues : one with my local environment which causes the error message but does not prevent the browser to open, and the one with tilt because i cannot see anything on the web page ( Note : my environment is a virtualbox ubuntu VM |
I found this github issue - intel/libva#278 - but TBH it's a bit beyond me. Ya, if you're running tilt in an ubuntu VM, you have to open Tilt's dashboard on the VM's One way to do this is to run the browser in the VM. Another way is to start tilt with |
@nicks yes I was already using the brower inside the VM, so my localhost is the localhost of the VM But the FYI, I checked to try to understand the difference between both command, and it seems to be the URL exposed by tilt by default : tilt up => expose "localhost" and does not work on my VM
tilt up --host 0.0.0.0 => expose 127.0.0.1 and works on my VM
Anyway thanks, i can continue my evaluation ;) |
yay! ya, VM networking is odd. closing... |
Expected Behavior
the Hello world tutorial has no error
Current Behavior
Following the instructions here :
tilt up
Context
tilt doctor
OutputAbout Your Use Case
Just trying to evaluate Tilt
The text was updated successfully, but these errors were encountered: