Sounds interesting. In that case, how could I configure the agent to use such user?

Well nothing special, only says it's nfs version 3

So what can I do?

But that's not the case

I'm not sure I fully follow

The agent cannot use another user (it literally has no way of getting credentials). I suspect this is all a by product of the actual mount point)

correct

Could you maybe check this?

You actually have to login/ssh under said user, have another dedicated mountpoint and spin the agent from that user.

If I'd be exact that's a trains agent task that creates in a new subprocess another trains agent task

This is an OS restriction 😞

why would root cause the user to become nobody with group nogroup?

It is exactly the case, they inherit the cron service user (uid/gid) which would look like nobody/nogroup

what does mount -a return ?

They all "inherit" the same user / environment from one another

If that's so, why would root cause the user to become nobody with group nogroup?

Well the original task is run with my user

I see. Let me try that and get back to you

Yes, it could, crontab uses the user it is running from (root if used with sudo)

mountpoint -q A && echo "" || mount B A

Changing the mountpoint for the agent is not possible

You cannot change the user once you have mount the shared folder with wither CIFS or NFS

Run a remote task with trains agent that would create inside another task that would again run remotely as well and check the permissions of the second task created file?

nfs version 3

That's the thing, NFS will automatically set file access and flags based on the mount options you cannot change them post mount.
How about creating a new user just for the agent, it makes sense from security / credentials perspective

Well nothing special, asks for password for some mounts, but not the one discussed, I am also required to run mount -a via root.

SmarmySeaurchin8 what's the mount command you are using?

create inside another task that would again run remotely

This Task will be run on another node, user / permissions will be dealt with by the agent on the other node running the Task

For me

My bad I meant the output of mount

So I'd guess they would inherit my user as well

Hmm, could this happen because I bring the agent up through crontab on reboot then? (with sudo crontab -e)