Unlock Linux automation with 21.8 Robot!

News Product News
,
#26

Thanks for your answer. Should I change this:

ORCHESTRATOR_URL=“https://cloud.uipath.com/orgname/DefaultTenant/orchestrator_”?

#27

Hi @Ray_Mueller,

Yes, that is the correct format for your orchestrator URL. It should be like this image

Best regards,
Andrei

#28

I am confused. The format used is not correct, but the unattended sessions are in status connected.

Can you please explain credentials-less robots a bit more.

#29

A post was split to a new topic: Learning advise for a beginner

#30

Hi @Ray_Mueller,

You are using classic folders and this is why the Robot shows it is Disconnected. The Linux and credential-less Robots are to be used with Modern folders.

Best regards,
Andrei

1 Like
#32
#33

@erghe

Hi, it works!

1 Like
#34

Hi everyone,

We published a github repository where you can check how to build a docker container that uses our UiPath Robot and Java/Python environment or the self-signed certificate from your private Orchestrator.

Best regards,
Andrei

3 Likes
#35

Nice, thanks for sharing!

-Eero

#36

@erghe @ElenaBuchir @Ryan_Rush

Hello Elena, Andrei and Ryan,
today I was participant of the great introduction of the assistant for macOS. As far as I understand it correct the same what is true for Linux is also true for macOS: “When Linux/macOS environments are used, robots can only run processes developed as cross-platform in Studio and do not require UI Interaction.” I guess the two assistants are very similar. A question that is now bothering me: Do the assistants support additional NuGet packages, which are transported from the orchestration to the assistant when they are needed? If this were possible, we would have great possibilities to create one NuGet package that can work on all platforms and contains all we need.
Thanks and best regards
Stefan

#37

Sweet! Wanted to get into it, and now I did. Output of a Bot performing Linux file create + write operation on the default WSL 2 Alpine Linux container. :slight_smile:

Had to install nano that I’m used to working with (in Debian and Raspbian) in the Alpine container.

image
image2322×1277 46.5 KB

Cheers! :+1:

3 Likes
Forum Engagement Daily Reports
#38

Any reason why a File Create activity would not work on Debian Linux?

Set up:

  1. I have Debian Linux installed and integrated Docker with it
  2. The container starts up with a volume mounted to a folder in Debian
  3. As seen from the Debian prompt below, Automations run and I am able to get the UiPath logs to persist in the Robot.log file

If it’s possible to write to this volume, then why can’t the Create File activity create a file at the same location? I get this error:

message: Create File in Linux File System: Could not find a part of the path '/home/thanosdebian/share/UiPath/Logs/Debian_TestFile_01242022_092825.txt'.
level: Error

image
image1385×560 37.9 KB

Thanks!
Andy

#39

Hi @AndyMenon,

I don’t think the path you are trying to write to is available in the container itself. How does the
docker run command looks like? It seems to me that you mounted the logs folder to the host folder: "/home/thanosdebian/share/UiPath/Logs/" and you are trying to access the host folder path in the container, instead of accessing "/root/.local/share/UiPath/Logs/".

Best regards,
Andrei

#40

Hi @StefanSchnell,

The docker container for Linux is purposed for unattended automation (there is no assistant on Linux, yet), while the Mac story is purposed for attended automation.

To answer your question, you can make a cross-platform library that you can use in your cross-platform projects. You can just publish this library to your Orchestrator and it will be available for all of your cross-platform automations.

Best regards,
Andrei

1 Like
#41

Hello @erghe,

I have installed Debian separately from the Windows Store and then integrated Docker with it. Therefore I have the native Alpine Linux where everything works as expected. I start the docker container for Debian like so:

docker run
-e LICENSE_AGREEMENT=accept
-e MACHINE_KEY="{my_machine_key}"
-e ORCHESTRATOR_URL="https://cloud.uipath.com/myService/myTenant/orchestrator_"
-v /home/thanosdebian/share/UiPath/Logs:/root/.local/share/UiPath/Logs/
-ti registry.uipath.com/robot/runtime

As shown in the screen grab in earlier post, when the Automations run, the container is able to write the Robot.log file to the Debian path /home/thanosdebian/share/UiPath/Logs.

In the automation, the Create File Activity I try to write to /home/thanosdebian/share/UiPath/Logs.

I maybe going wrong here and will give this a shot and report back.

Thanks,
Andy

#42

SUCCESS! :smiley: Thank you @erghe! I must have been standing on my head when I got the whole thing backwards. I changed the input argument in my automation to use the Alpine Container path instead of the Debian host path!

image
image1900×462 27.6 KB

And when opened in nano on Debain:

image
image2322×1280 72.4 KB

Nice!

#43

Has anyone deployed this to Openshift?

#44

Hello Andrei,

Can you suggest any specific H/W and Linux OS flavor to be used for the Linux Robot? I was trying to check the documentation and it gave only the below prerequisite and do not find any specification for docker environment.

Regards
Balram

#45

Hi @balaraman.ramiya,

There is no specification on HW and Linux environment because you can choose whatever you want. The only current limitation is that you can run the UiPath Linux Robot only on x64 bit architecture.

Best regards,
Andrei

1 Like
#46

Thanks! Andrei.

Regards
Balram