Not at all! I think the idea you have is quite good, to have a ready-made container to run xrootd as a service. I will close the PR, but in the upgrade we are doing for the CI I will see if we can improve the defaults in the containers to make it easier to run unprivileged and maybe consider also providing a Dockerfile specifically for this case which installs a pre-built version of XRootD using our RPM repositories rather than building it from source.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/2066#issuecomment-1663812785", "url": "https://github.com/xrootd/xrootd/pull/2066#issuecomment-1663812785", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1