brambo23

I noticed conda isn't installed on this docker of jupyterlab. Is there a way to install conda onto this package or should I look for a different docker container?

What I like the most about Unraid is the ease and simplicity of managing and maintaining a media server (from hard drive upgrades to swapping out drives, to dockers and more) What I would like to see in the unraid future is to keep up the good work with stability and support!

Again nevermind. I'm slowly figuring out how to use the letsencrypt docker from the spaceinvaderone tutorial

I am able to connect to a room using the url IP:<port>/slserver but i can't get letsencrypt to work, it can't connect to the server with the docker, any thoughts on that part?

So I was going by the instructions on the docker which read: I changed the port based on the default to 8088 and 8089 i tried using a domain and just my local ip, but i couldn't connect to the room. Looking at my docker log it reads: Do i have to change the settings inside the docker itself? I too cannot get letsencrypt docker to create a cert for it. I have set the proper port forward rules. I am a noob when it comes to this stuff so i'm pretty sure i'm just not smart enough to figure out what i'm doing wrong

To add insult to injury I didn't realize this entire time that I was in "Basic view" of the docker and was not able to see the "extra parameters" field. Working great now. Thank you for putting up with my stupidity.

Sigh I knew it was something stupid. The reason I kept getting the same error no matter what I did was because I named the key under the new variable gui "Extra Parameters" and having that space caused issues. Changing Extra Parameters to EP finally produced something different. Also a second note I noticed i was naming my interface bro instead of br0 so im sure I would be getting issues once I changed EP. Haven't successfully gotten pipework to work well for me yet, but now i can start troubleshooting it properly.

Thank you both for the replies. I changed it to this: -e 'pipework_cmd=bro.5 @CONTAINER_NAME@ 192.168.5.40/[email protected]' -e 'pipework_cmd=bro.5 @CONTAINER_NAME@ 192.168.5.40/[email protected]' but I am getting the same error as before. I'm sure there is something very stupid i'm missing

I am currently trying to use Pipework for my docker containers. I'm trying to use a vlan interface bro.5 which I confirmed works by setting up a VM on that interface. I added a extra variable -e 'pipework_cmd=bro.5 MineOS 192.168.5.40/[email protected]' the Pipework log states that /entrypoint.sh: line 363: export: `Extra Parameters=-e 'pipework_cmd=bro.5 MineOS 192.168.5.40/[email protected]'': not a valid identifier What exactly am I doing wrong? I tried some other variants of the command line but i get the same eror everytime I set the network type to none. I also tried just using the bro interface on dhcp and it did not seem to work either. any help would be appreciated

I seem to be not having the same success as you. I changed the VLAN to static but my vm still couldn't access anything on the network (even the gateway)

To clarify, you're saying to setup a static IP in the network settings of unraid itself? or setup static IP in the network settings of the VM? I'm currently having a similar issue where unraid will not grab an IP on the VLAN i had setup on my router ( Ubiquiti edgerouter connected to a smart switch) and my VM's also won't grab an IP either from the DHCP server.

No, never got it to work, I ended up doing a samba share to get the same effect.

Hello, I have just started using the VM feature in UNraid6 and loving it so far. I have a VM I want to use to basically run some python code to download some files every day and add them into a share on the unraid server. I created a share, named it "block1" Inside of the VM settings i went to "unraid share" and added it /mnt/user/block1 and gave it the tag "block1" I'm running Ubuntu server 14.04 LTS on the VM and when I tried to find the folder for this, I couldn't. I followed the links from this post: http://lime-technology.com/forum/index.php?topic=45032.0 but none of those settings seem to work. The share is showing up in my XML file: <filesystem> <source dir='/mnt/user/block1/'/> <target dir='/home/brambo/block1'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </filesystem> But it's not showing up in the VM itself (at least from what I can see). Any guidance/suggestions would be appreciated.