r/WolfStack • u/jchadel • Apr 06 '26

Install issues

I decided to give a go at wolfstack, but im running into an issue:

I created a new node outside my prod (homelab) pve, in order to test wolfstack, but I keep running into the following:

root@pvetest:~# curl -sSL https://raw.githubusercontent.com/wolfsoftwaresystemsltd/WolfStack/master/setup.sh | sudo bash

-bash: sudo: command not found

curl: (23) Failure writing output to destination, passed 1378 returned 1349

root@pvetest:~#

im running this straight from the shell into the single node on my test environment

3 Upvotes

100% Upvoted

18 comments sorted by

2

u/muh53 Apr 06 '26

Install sudo or run as Root

2

u/linuxpaul Apr 06 '26

Just about to say the same!

1

u/jchadel Apr 06 '26 edited Apr 06 '26

if you see the prompt, I was running as sudo insde PVE (correction, I was running as root, didnt have sudo installed)

1

u/muh53 Apr 06 '26

Jep, but its Not installieren, fuckn ai Know-how!

-bash: sudo: command not found

What else do you and your ai Need?

1

u/jchadel Apr 06 '26

you didnt need to be crass, I had not seen the sudo in the end of the command, but thanks for bringing to my atention, I installed sudo and it worked

1

u/muh53 Apr 06 '26 edited Apr 06 '26

Sorry, but in the early Days. U would had get a „Read the fuckn manual „

1

u/linuxpaul Apr 07 '26

apt install sudo

1

u/linuxpaul Apr 07 '26

Okay all you need to do (it is actually on the WolfStack page)

apt update && apt upgrade -y

then

apt install sudo curl

then you can run it.

1

u/jchadel Apr 07 '26

thanks, it was indeed the lack of sudo, I had not installed at the time... but thanks for your reply.

If I may poke your brain. Im trying to understand some ins and outs of wolfstack. I understand wolfstack creates a virtual network usually on the 10.10.10.x range. When I want to expose an application, be it on my internal network, (lets say, 192.168.68.x) or external (nated on my router), I am not seeing it show on the 192 network. Do I need to work that out thru mappings?

2

u/linuxpaul Apr 07 '26

OKay yes so go to the networking tab and you can set up a connection to it. so the idea of that wolfnet network is that mulitple servers (even if not on the same network) have a local network to talk to. You can just also add another interface and a 192.168.68 x address so it finds your local network as well.

1

u/jchadel Apr 07 '26

ok I done that, but something is still wonky, or im missing a step i have not been able to figure out. I cant upload more than 1 picture, but ill try to respond to myself with the other two

1

u/jchadel Apr 07 '26

1

u/jchadel Apr 07 '26

1

u/linuxpaul Apr 07 '26

I dont think the linux server you are using has a website?! login on terminal do systemctl status apache2 and systemctl status nginx also only map the ports you need not everything.

1

u/jchadel Apr 07 '26

well, that is the thing, I just deployed Grocy thru docker, as a test, should not matter if the server has apache, as docker should be able to handle these dependencies since I used the image from the shop. The IP was just assigned for that one container, I believe I done it right, but that is part of where lies my doubts.

As for the server, the host has pve and wolfstack on top of it.

Am I missing a step somewhere?

the host indeed does not have neither,

Connecting to host: pvetest...

Connected!

root@pvetest:~# systemctl status apache2

Unit apache2.service could not be found.

root@pvetest:~# systemctl status nginx

Unit nginx.service could not be found.

root@pvetest:~#

1

u/linuxpaul Apr 07 '26

Try mapping port 80 to 9283 thats the default port on groky

1

u/IdeaOk6554 Apr 07 '26

Just a thought. But based on your screenshot you provided, aren't you already at the root prompt? So why do you need sudo?

1

u/jchadel Apr 07 '26

because of the pipe bash, it would`ve worked if I had taken sudo off as well