Forum Replies Created
I’m glad things worked out for you. Your testing and @Sean Robinson’s helped me improve the code also. I hope other people can test this project too so I can adjust the repo for the multiverse of setups out there. 😛
Hey guys! Sorry for the delay answering. We are at Carnival Holidays in Brazil so I’ve been absent from my dev activities.
Anyway, @hulaboop I think I’ll need more information about your setup to help you. Could you tell what is your hardware configuration?
lspciwill give you an output that you can paste here.
Also, are you using which Linux distribution? (that should not matter, but the more info we have the better)
lsb_release -ais an output you can paste here
And finally, are you building your image using
Ok! That’s an issue with the application trying to communicate with your X server. Does docker have permission to access your x server?
Hey Sean Robinson thanks for the help.
Yes, your solution should work. So I’ve created the SARndbox-2.8/ folder and added both empty BoxLayout.txt and ProjectorMatrix.dat to avoid this kind of error.
Thanks for testing hulaboop! Do a git pull on your repo to download the files and try again, please.
Hey! I see what happened there, indeed just “make” was needing sudo access. I’ve removed “installudevrules” from the “all” target. Now you can type “make” without sudo and it should build the image without this error.
But make sure that you already done “sudo make installudevrules” before “make”.
Hi! Yes, of course I can explain!
“Could you give a non-technical explanation of sarndbox-docker?”
Well, sarndbox-docker is a containerized ubuntu running sarndbox. You can imagine it like a Virtual Machine running Ubuntu 18.04 with only Sarndbox installed on it.
“Is this for building a package? Or will the container run the sandbox software, too?”
Well, it can be used to build sarndbox, but the way it is written now, sarndbox is built alongside container image creation (a container image is like a saved virtual machine, once it “reboots”, it returns to that saved initial state). Currently, the container is made to run sarndbox and its calibration tools.
“If I run an Ubuntu 18.04 container, do I need to update and manager software for two systems? One in the container and one on the host?”
No! And that’s the funny part. Once you build that “image” that I mentioned before, the software keeps working with your host. You can update it, install or remove software, leave it any way you like, as long as docker is installed, sarndbox-docker should keep working normally. You could even export that image and transfer it to another host, this new host could be a newer Ubutu, older Ubuntu, Fedora, Alpine, etc (you name it), you just need docker and docker-compose installed. Of course there are some caveats (like always depending on Nvidia hardware to see water flow simulations), but that should be on sarndbox’s side. I mean “should” because I have not tested sarndbox-docker in all different situations yet, only on my host.