Wayk Bastion Linux Install instructions deviation

Wayk Bastion Linux Install instructions deviation

avatar

So I figured out that the powershell instructions work for both Linux and Windows after installing Powershell on Linux, followed the whole thing, I setup let's encrypt using DNS verification because the console wasn't ready yet at that stage of the instructions, got the web console up and running and configured what I could into the console, and everything went fairly smooth, however! The last part of the instructions seem to pertain to Windows only, specifically the part about configuring the whole thing as a System Service. When I get to the point where the instructions say to issue the following commands...

PS > Set-Location $ConfigPath
PS > Register-WaykBastionService -ServicePath $ConfigPath
"WaykBastion" service has been installed to "C:\ProgramData\Devolutions\Wayk Den"
PS > Get-Service WaykBastion

instead, what I get is this....
forum image

So how do I proceed in Linux with configuring this whole thing as a service or launch at startup, because it feels like if I restart my server I'll have to issue some configuation command before I can just start it up again and I'd definitely want it to start up automatically.

I'm sure it's simple, but honesly I'm not fully understanding how this whole thing works. It's a quasi windows/linux/docker package that is dealing with stuff that is not anything I've dealt with before. I'm a Linux newbie and this is not like anything I've seen on top of it all.

SideNote: There's misspelling on the last sentence of the instructions. The word "never" I'm sure was supposed to say "newer". I didn't find any feedback links on the instructions page so I figured I'd throw that detail in here maybe it'll get to whoever does that part.

"You can also update the service wrapper executable when never versions of the cmdlet are published by calling Register-WaykBastionService
again."

All Comments (1)

avatar

Hi,

You are correct, the Register-WaykBastionService is unfortunately a Windows-specific feature. We still have to provide a convenient way to automatically call "Start-WaykBastion" on system startup. The only reason why you need to call Start-WaykBastion once the containers have been started is because we launch them in a specific order and Docker doesn't let you define dependencies. One possible workaround that could work is to call Set-WaykBastionConfig -DockerRestartPolicy 'unless-stop' which will tell Docker to restart the containers and keep them running unless they are explicitly stopped. On a system restart, you may get a few failures in your logs (since they will be started in a random order), but it should eventually get back on its feet.

I suggest you confirm that everything works with Start-WaykBastion and connecting to the web interface before trying to configure it such that it starts automatically.

Best regards,

Marc-André Moreau