Just checked the kerneel config and IPV6 is not set. Wonder if that's the issue.

 

 

i'm not up on kernel stuff, but it does seem a likely candidate given we are both experiencing issues related to ipv6.

how about explicitly disabling ipv6 in the container, is that possible ?

It is by default, the kernel controls everything. If the kernel from unraid doesn't support ipv6 it means we are screwed. Unfortunately the instructions to compiling your own custom kernel for unRAID are a little outdated.

Okay new image is being built on the docker servers as I typed this image. I forked the phusion base image and updated the base os to utopic so that I could an x11vnc binary where I could disable ipv6 from the command line. I tested and so far it works, so please report back. Remember you can now access the container using rdp as well if you map the port 3389.

i may have "fixed" my issue too, i found the config file for building the node packages and took out the references to ipv6

 

it's not throwing up any errors so far, just having issues connecting to the server, but i had this before where i got the build commands in the wrong order.

i just forked this , hope you don't mind.

 

was going to try and pick it apart , use your compiled binaries and use it for single use containers at a later stage.

Nope by all means, we are here to help each other out.

Just updated TMM and it works fine through browser.

 

Tried RDP and cant get to connect to the server. Trying to connect from a mac and using the ip address and port. It says connection refused. Is there a username/password that I should enter?

My mistake I never configured the port Now that its configured I'm able to connect

Awesome, happy to hear.

Awesome, happy to hear.

 

Huge thanks to you Loving RDP....so much better than the browser

Good, let me know if there any additional adjustments you feel are necessary. PS you can make it accessible through a browser using rdp by using the guacamole container.

i've built a container out of calibre, (mainly for testing), using yours as a base.

 

the only thing is though, i don't like the desktop switching in openbox, do you know there is any way to force it to have only one so it doesn't switch ?

 

EDIT: think i may have found it.

 

http://openbox.org/wiki/Help:Configuration#Desktops

Should I take out tinymediamanager and make a base for just the gui part, so that you can fork that and make pull request for additions, and adjustments?

Should I take out tinymediamanager and make a base for just the gui part, so that you can fork that and make pull request for additions, and adjustments?

 

i took the tmm container apart and put it together into a more traditonal Dockerfile as i find that easier to work with personally.

 

i've been trying a couple of things, first i went back to "stock" phusion-base and added in the utopic repos to install x11vnc and then took them out again to call everything else, it starts but i'm having issues with setup screen on calibre, not certain if i've cocked up something else, looking later at that.

 

if that don't sail, i'll try and compile another x11vnc from a writeup dated last week sometime specifically to address ipv6 issues

 

 

http://mispdev.blogspot.co.uk/2014/04/x11vnc-avoiding-buffer-overflow-when.html

I saw that, you don't want to move away from the phusion image? the only thing I change from forking phusion 0.9.16 was changing the base and nothing else at all. Have we drawn attention to Dev team about compiling the kernel with ipv6 support so that we don't have to do all these work around?

By the way is there a link to your container? I would like to review and contribute if possible?

I saw that, you don't want to move away from the phusion image? the only thing I change from forking phusion 0.9.16 was changing the base and nothing else at all. Have we drawn attention to Dev team about compiling the kernel with ipv6 support so that we don't have to do all these work around?

 

i think it would be good to stay on stock phusion base, as regards to the dev team, i've not made any approaches.

By the way is there a link to your container? I would like to review and contribute if possible?

 

 

i'll link you to the github, it's not in dockerhub yet.

https://github.com/sparklyballs/docker-containers

 

it's the calibre-desk folder there.

Cool! And Thanks.

Updated now to the latest version and TMM server is not reachable. Both through RDP and Browser. From the log file

 

ddxGiveUp:
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.

Fatal server error:
Could not create lock file in /tmp/.tX10-lock

Sorry, I will test right now. I made more massive changes to increase performance.

Sorry, I will test right now. I made more massive changes to increase performance.

 

No problem Was just reporting

Okay should be building now, test the web interface now. It runs full rdp communication.

Havent got the update yet. Will check and post as soon as it is online.