ProGet: 25.0.9 with PostgreSQL
Maven work as mirror, link to https://repo1.maven.org/maven2
Invalid Versions: not block
Nonstandard Files: not block
Vulnerabilities Rules: all not blocking

Artifacts likes: http://127.0.0.1:8080/feeds/MavenMirror/io.r2dbc/r2dbc-bom/Arabba-SR13 can view meta info
Download pom file like: http://127.0.0.1:8080/maven2/MavenMirror/io/r2dbc/r2dbc-bom/Arabba-SR13/r2dbc-bom-Arabba-SR13.pom will response
Request finished HTTP/1.1 GET http://127.0.0.1:8080/maven2/MavenMirror/io/r2dbc/r2dbc-bom/Arabba-SR13/r2dbc-bom-Arabba-SR13.pom - 302 0 - 3.3826ms
will redirect to http://127.0.0.1:8080/maven2/MavenMirror/io/r2dbc/r2dbc-bom/Arabba-SR13/r2dbc-bom-Arabba-SR13.pom/ , this url pom file treated as directory, download fail, block build

inedo/proget:5.3.17
Host: CentOS Linux release 7.8.2003 (Core)
Docker: version 19.03.5, build 633a0ea

Reference office Linux docker documentation， docker run inedo/proget:5.3.17，

docker logs proget without any error， but WebApplication not started/Listen to port 80.

docker exec -it proget bash, use dotnet ProGet.WebApplication.dll manual start Web, start with error: "Access to the path '/proc/1/map_files' is denied"
ref github issues: https://github.com/dotnet/dotnet-docker/issues/644
this may miss WORKDIR in Dockerfile.

Now we create a local Dockerfile with content:

FROM proget.inedo.com/productimages/inedo/proget:5.3.17
WORKDIR /usr/local/proget

then build and run, can resolve this problem,
can you add WORKDIR official to resolve the compatibility with CentOS 7.

We run ProGet mono docker on centos 7.4, network architecture is:
user -> Kong(Nginx) -> ProGet

Web.BaseUrl is set to: https://proget.company.com

docker login -u admin or other users, always response HTTP 401.
We set docker proxy, use fiddler capture https flow, the requests sequence seems like this:

1. docker request https://proget.company.com/_v2/xxx, proget response 401, with AUTH header and realme info, response header is same to Web.BaseUrl's value
2. docker request with basic auth, proget response bear token
3. docker reqeust with 2. bear token, proget response HTTP 401, login fail.

ProGet 5.3.15, 5.3.17 have same issue, change to use .net core can solve this problem.