No, the task is outside of the container and this task works also outside of the containers.
I saw that access_role has this EXECUTE privilege and this is why it works with it.
I'm glad that it worked for us at this moment, but if you say, we shoundn't use this role, I need to find an other solution. ![]()
(But the name of this role sounds so apposite.)