-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
App Request: Firefox #264
Comments
You'll have to provide some argumentation as to what purpose this would serve in a media box context, because it's far from obvious. |
No worries. I was able to hack together an yml that works. My use case was to access many of the apps using the short name and local port so I don't need to expose the apps directly to the net. Also useful to have a browser with all your apps/links/favorites configured and consistently available from anywhere. It also allows accessing sites from public/other networks (e.g. traveling) without the need for a vpn while still "proxying" the traffic. Last, some trackers don't like login from multiple ips. The browser allows login from the same ip as the feeder (assuming you run feeder from same box.) It's a browser running in a vnc remote session served over http/https. I'm sure there are other benefits I'm not thinking of but a remotely accessible browser can have lots of utility I'm sure. :) |
To that first point at least, you could use a layer 4 proxy. But yeah, fair points I suppose. If you have a working yml it sounds like you've already done most of the work for submitting the role yourself. |
I am completely github dumb, just fork and submit a change request? |
Step by step here: |
I've begun work on this role btw. Not a problem if you still want to give it a stab though—just let us know. If not, consider sharing your yml so I see if I'm missing anything. |
Here is tasks yml:
|
Here is defaults yml:
|
I should have noted I just copied from another app and hacked it up, so there could be extra stuff in there that isn't needed, but it works :) |
Oh this is awesome, thanks for the pointer! |
That's how I do it and how it's usually done. 😉 |
Rationale for using jlesage/firefox rather than linuxserver/firefox? |
For whatever reason, I couldn't get the linuxserver one to work without --priveleged or - seccomp:unconfined flags even though they are optional. Also, if bypassing authelia, the way jlesage/firefox does the vnc password is much cleaner imo. Linuxserver container requires you to create a password/hash file. jlessage you put a password in a cleartext file in the config dir, on boot it will digest the pw, hash it, write that out to a new file and delete the cleartext file. Changing the pw is as easy as creating the file again and restarting container. Last, the jlesage container gives you the option to pass port 5900 through, which is the vnc protocol. Using firefox via web browser on mobile is painful and pretty much unusable, but using a vnc client on mobile is tolerable. One thing I missed, is apparently these containers can use /dev/dri for hw acceleration. That is not mapped in mine. |
It seems like you have already started work on this? Is that correct? |
Yes. Got a lot on my plate right now but I do have it planned. |
Cool, it's marked WIP so shouldn't be picked up randomly by anyone else without realising it's underway. |
Browser in a vnc style window but accessible remotely from another browser
https://hub.docker.com/r/linuxserver/firefox
The text was updated successfully, but these errors were encountered: