Could you please tell us the agent version in which you are facing this issue?
We had fixed this issue and this would not be occurring in the latest agent versions.
Note: Our latest Linux agent version is 17.7.1
Hope this helps. Let us know for further queries, if any, in the below thread.