OPC UA, as a communication standard, is platform independent.

QuickOPC-UA, for integrating OPC UA client functionality into .NET-based application, is supported on Linux.

- opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User%2....html#Operating%20Systems.html
- learn.microsoft.com/en-us/dotnet/core/install/linux?tabs=netcore2x

Best regards

Hello,
I do not understand the question, because "COM" (Microsoft Component Object Model) can be used to

1) Communicate to the OPC server. This is the case of OPC "Classic" specifications. However, you mentioned QuickOPC-UA, and therefore OPC UA. And OPC UA is not based on COM. So in this case the question makes no sense.
2) Communicate between the OPC client toolkit, and the actual application. COM is not available on Linux so in this case the question makes no sense either.

The only theoretical possibility where COM can be used on Linux (but *not* with OPC UA) is to connect to OPC Classic servers on a network from a client on a Linux machine. That is doable because the DCOM wire protocol has been made public, and there are even some non-Microsoft implementations of it. We have no plans to support that.

Best regards