csmccarron Posted June 18, 2017 Share Posted June 18, 2017 I would like to suggest that kernel support for IA32 Emulation support be enabled. This would allow docker that need 32 bit emulation enabled in the kernel to run. No packages or libraries need to be added to the unRaid operating system. If the docker has a copy of the 32 bit libraries and IA32 is enabled in the kernel the 32 bit binary inside the docker will execute. I have tested this on an unRaid 6.3 slackware64 VM with the results of the steps and test result located here. If someone could point me to instructions on how to rebuild the unRaid 6.3 kernel and build the boot image, I would be more than happy to do further real world testing this on my unRaid server. Quote Link to comment
Squid Posted June 18, 2017 Share Posted June 18, 2017 Just now, csmccarron said: If someone could point me to instructions on how to rebuild the unRaid 6.3 kernel and build the boot image, I would be more than happy to do further real world testing this on my unRaid server. talk to @CHBMB 1 Quote Link to comment
BRiT Posted June 18, 2017 Share Posted June 18, 2017 @csmccarron Maybe if you ask kindly to @CHBMB he could enable IA32 on his DVB builds too. Maybe they could serve dual-purpose until such time as it's built into the main build. Quote Link to comment
csmccarron Posted June 18, 2017 Author Share Posted June 18, 2017 49 minutes ago, BRiT said: @csmccarron Maybe if you ask kindly to @CHBMB he could enable IA32 on his DVB builds too. Maybe they could serve dual-purpose until such time as it's built into the main build. PM already sent Quote Link to comment
csmccarron Posted June 25, 2017 Author Share Posted June 25, 2017 I have built a test kernel based on unRaid 6.4 rc6 and enabled IA32 Emulation. This configuration option allows the kernel to emulate a 32 bit environment. I DID NOT have to install any additional libraries in the unRaid operating system. I am now able to run 32 bit binaries inside dockers that contain the 32 bit libraries. I have been testing with TuRz4m Ark Survival docker. I am willing to share my unRaid 6.4 rc6 test kernel to anyone that would like to test it out for themselves. All you need to do is upgrade to unRaid 6.4 rc6 then replace the bzimage, bzmodules, and bzfirmware files with mine. PM me if you would like me to send them to you. NOTE: This test kernel also has USB Attached SCSI (CONFIG_USB_UAS) protocol enabled for more testing that I am going to do when I get home. 1 Quote Link to comment
Djoss Posted July 9, 2017 Share Posted July 9, 2017 It would be nice to have 32-bit support by default. I have a docker container for tsMuxeR that is not working on unRAID because tsMuxeR is a 32-bit application only... Quote Link to comment
bonienl Posted July 9, 2017 Share Posted July 9, 2017 Wait for next RC of unRAID 6.4... 1 Quote Link to comment
csmccarron Posted August 3, 2017 Author Share Posted August 3, 2017 This is working, thank you! Quote Link to comment
Boo-urns Posted March 23, 2018 Share Posted March 23, 2018 (edited) On 6/25/2017 at 11:37 PM, csmccarron said: I have built a test kernel based on unRaid 6.4 rc6 and enabled IA32 Emulation. This configuration option allows the kernel to emulate a 32 bit environment. I DID NOT have to install any additional libraries in the unRaid operating system. I am now able to run 32 bit binaries inside dockers that contain the 32 bit libraries. I have been testing with TuRz4m Ark Survival docker. I am willing to share my unRaid 6.4 rc6 test kernel to anyone that would like to test it out for themselves. All you need to do is upgrade to unRaid 6.4 rc6 then replace the bzimage, bzmodules, and bzfirmware files with mine. PM me if you would like me to send them to you. NOTE: This test kernel also has USB Attached SCSI (CONFIG_USB_UAS) protocol enabled for more testing that I am going to do when I get home. Apologies for reviving an old thread, however @csmccarron are you able to provide some guidance on how you managed to set up TuRz4m's Ark Docker. I enabled dockerhub searches in CA, and attempted to add the container with the basic ports described here: https://hub.docker.com/r/turzam/ark/ However regardless of what I put in there, i get an error "/usr/bin/docker: Invalid containerPort: ${STEAMPORT}.". It seems like whatever I put in as the ${STEAMPORT} or ${SERVERPORT} translates into the first part of the code but not the second '27015:${SERVERPORT} and that's what seems to be causing the error. Please note I am an unRaid noob, and I have no experience with linux command line, but i'm willing to learn! Most of my setup has been using SpaceInvader One's extremely helpful vids. Context: Am currently running an ARK server on a Windows VM, looking to move to docker. EDIT: Runing unRaid 6.5.0 TIA! Edited March 23, 2018 by Boo-urns added unRaid version Quote Link to comment
Squid Posted March 23, 2018 Share Posted March 23, 2018 It's expecting you to substitute ${....} with an appropriate port number Quote Link to comment
Boo-urns Posted March 23, 2018 Share Posted March 23, 2018 26 minutes ago, Squid said: It's expecting you to substitute ${....} with an appropriate port number Apologies, I mixed up the previous 2 screenshots. The first image above was the default settings screen. I have tried entering "${27015}", "27015", "{27015}" to no avail. The below is what I enter in the setting vs the error that is produced. Quote Link to comment
Squid Posted March 23, 2018 Share Posted March 23, 2018 They all have to be just a number no $, { or }. Quote Link to comment
pwm Posted March 23, 2018 Share Posted March 23, 2018 A recommendation is that the GUI displays the field in evil red as long as the port numbers aren't valid integers within allowed number range. And preferably that it isn't possible to save if any of the ports are invalid. 1 Quote Link to comment
Boo-urns Posted March 23, 2018 Share Posted March 23, 2018 52 minutes ago, Boo-urns said: I have tried entering "${27015}", "27015", "{27015}" I have tried that as I mentioned above, using 7778 as both of the STEAMPORTs and 27015 as both SERVERPORTs. It still gives me the same error "/usr/bin/docker: Invalid containerPort: ${STEAMPORT}.". Quote Link to comment
bonienl Posted March 23, 2018 Share Posted March 23, 2018 9 minutes ago, pwm said: A recommendation is that the GUI displays the field in evil red as long as the port numbers aren't valid integers within allowed number range. And preferably that it isn't possible to save if any of the ports are invalid. The better recommendation is that container authors preset the correct values already. That is the whole purpose of the XML file, unload the burdon from the user. 1 Quote Link to comment
pwm Posted March 23, 2018 Share Posted March 23, 2018 Just now, bonienl said: The better recommendation is that container authors preset the correct values already. That is the whole purpose of the XML file, unload the burdon from the user. No - not better since it's a completely different issue. Good defaults will help, but since people are expected to be able to change values the GUI should try to help by catch invalid values. Quote Link to comment
bonienl Posted March 23, 2018 Share Posted March 23, 2018 19 minutes ago, Boo-urns said: I have tried that as I mentioned above, using 7778 as both of the STEAMPORTs and 27015 as both SERVERPORTs. It still gives me the same error "/usr/bin/docker: Invalid containerPort: ${STEAMPORT}.". Click on "Edit" for a particular setting, this will open a second window. Can you show what it looks like? Quote Link to comment
Boo-urns Posted March 23, 2018 Share Posted March 23, 2018 see below. Also, scrolling through the https://hub.docker.com/r/turzam/ark/ page, in the Variable section it states the below. Is it likely this is the cause? SERVERPORT Ark server port (can't rebind with docker, it doesn't work) (default : 27015) STEAMPORT Steam server port (can't rebind with docker, it doesn't work) (default : 7778) Is there an alternate means to install this docker using the command line on the page? Because it seems the script that runs when I get my error message is the same as the below, but with 7778:7778 defined rather than the 7778:${STEAMPORT} which is generated. Recommended Usage First rundocker run -it -p 7778:7778 -p 7778:7778/udp -p 27015:27015 -p 27015:27015/udp -p 32330:32330 -e SESSIONNAME=myserver -e ADMINPASSWORD="mypasswordadmin" -e AUTOUPDATE=120 -e AUTOBACKUP=60 -e WARNMINUTE=30 -v /my/path/to/ark:/ark --name ark turzam/ark Quote Link to comment
bonienl Posted March 23, 2018 Share Posted March 23, 2018 I didn't follow this whole conversation and jumped in at the very end. Are you using a preset template to install the container? If yes, it needs to be notified to the container author that preset values are completely wrong, these are not variables. Your option at this moment is to remove all current settings and create them again (see: Add another Path, Port, Variable or Device), which allows to set all the fields properly. 1 Quote Link to comment
Boo-urns Posted March 23, 2018 Share Posted March 23, 2018 3 minutes ago, bonienl said: I didn't follow this whole conversation and jumped in at the very end. Are you using a preset template to install the container? If yes, it needs to be notified to the container author that preset values are completely wrong, these are not variables. Your option at this moment is to remove all current settings and create them again (see: Add another Path, Port, Variable or Device), which allows to set all the fields properly. I don't believe i'm using a template per se, as i'm attempting to install via CA using the "search dockerhub" function. So I believe the template is created on-the-fly by CA, by converting the dockerfile. Disclaimer: this is a wild guess. I'll have a crack at creating the variables manually, in the mean time as the existing fields are incorrect, but *mandatory, what should I place in there? Quote Link to comment
bonienl Posted March 23, 2018 Share Posted March 23, 2018 6 minutes ago, Boo-urns said: I'll have a crack at creating the variables manually, in the mean time as the existing fields are incorrect, but *mandatory, what should I place in there? You need to delete them, they can't be used. 1 Quote Link to comment
Squid Posted March 23, 2018 Share Posted March 23, 2018 Ok. That's interesting . The conversion did work correctly and according to design but the dockerfile in its expose lines references environment variables. I'll have to issue an update to ignore things like that.In the meantime, all those ports that are coming up as ${} delete them completely. And then follow the directions on the docker page on how to set the environment variables (and add them as a variable in the template) 1 Quote Link to comment
Boo-urns Posted March 23, 2018 Share Posted March 23, 2018 Righto will do. Thanks for your help guys, i'll have a crack and see how it goes. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.