Expanding the project

[davidnewcomb]

Hi all, been using your app for a while and I have expanded it to include a few extra features that I would like to feed back into the project if you are interested.

1. Installation of VLC,
2. PulseAudio sound using 'native' or 'tcp' transport,
3. Build support files,
4. Extra running support files: ability to change external VNC port (Port Change Variable #19), external pulse audio port, modify display dimensions, shared folder on host system (via configuration file).
5. Better way to override configuration (still under development).

It's all on my vlc branch.

I've also been thinking that it would be nice to add support for other dark networks like Freenet, I2P, etc. or at least have them as 'switch-on-able' options. We could quite easily turn this product into the go-to app for dark browsing. Then we can all write books about it and go on the after dinner speaker's tour ;)

Thoughts?

Tagged in too @WhaleHub @korzq :)

[DomiStyle]

These look like good ideas but the first step would probably be to fork the baseimage, it's fairly outdated and in my opinion not up to the task of running a security related container like this. Also, it has no ARM version which makes it impossible to use this container on a Raspberry Pi.

I think that would expand the use cases of this image the most, a portable Tor browser image you can run on a Raspberry Pi sounds like a cool idea.

As for the other dark networks, maybe it's possible to generate separate images for them? That would use the strengths of Docker and keep them separate.

@DomiStyle Perhaps we could build a new Tor browser image based on Kasm Workspaces.

[davidnewcomb]

I hadn't heard of that project before but it looks interesting. I'll try a proof of concept with it.

[DomiStyle]

That does look interesting.

I will also snoop around in the Dockerfiles a little bit.

@davidnewcomb @DomiStyle Just curious, has either of you had any luck with running Tor Browser on a new base image?

Btw, I noticed that the image on Docker Hub hasn't been updated in a couple months, most likely because the autobuilds feature was removed from the free tier a while ago. One option to solve this problem would be to use GitHub Actions to build and push new images to the Docker Hub.

[DomiStyle]

@WhaleHub No, not yet.

Yes, I have a few Docker repositories that I need to switch over to Gitlab CI since I already know their syntax. Will be looking into that soon.

[DomiStyle]

Auto builds should work again. 10.5.5 needs to be retagged or just wait for a new Tor release.

[davidnewcomb]

@WhaleHub I haven't tried anything yet. Too busy with real work ;)

[vital987]

Checkout my project, it's noobly built but works like a charm, but their's no audio or media support however you can add it, cause I didn't felt it necessary to play media on a server via VNC. The project has basic necessary tools like browsers, file manager, text editor, terminals, telegram, etc.

[lawndoc]

Hey everyone, I ran across this repo after I started a similar project of my own. I actually use lsiobase/guacgui as the base image which is actively maintained. If you are all still interested in changing the base image and expanding this project, I'd be willing to pitch in here rather than reinvent the wheel over in my repo.

[lawndoc]

Actually forget what I said about lsiobase/guacgui being actively maintained. It looks like it's more out of date than this one's base image.