For me

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

Could you maybe check this?

My bad I meant the output of mount

what does mount -a return ?

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

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

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

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

This is an OS restriction 😞

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

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

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

SmarmySeaurchin8 what's the mount command you are using?

Well the original task is run with my user

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

Changing the mountpoint for the agent is not possible

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

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

So what can I do?

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

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

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

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?

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

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

I'm not sure I fully follow

But that's not the case

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