filehunter VS docker-registry-ui

If I understood correctly we have similar needs. I also needed something to search files in my nas. I decided to build search engine with multiple backend engines to index files, 100% open source and self hosted without privacy concerns. https://github.com/Ogefest/filehunter let me know if this project fits to your needs

Regarding file searching using web interface I started https://github.com/Ogefest/filehunter and I have plans to create web search engine for local/webdav/s3/ftp files.

At Github release page you can find binary to download and run https://github.com/Ogefest/filehunter/releases

Filehunter is available https://github.com/Ogefest/filehunter

If it's only the UX you care about then you can use the docker registry image which supports arm64 and then use a ux like docker-registry-ui and have a nice ui.

I didn't know Fleet. For my own images repos (not Dockerhub hosted) I use Docker Registry UI (on top of registry:2). It's tiny and works perfectly fine.

# required to avoid HTTP 411: see Issue #1486 (https://github.com/moby/moby/issues/1486) chunked_transfer_encoding on; # required for strict SNI checking: see Issue #70 (https://github.com/Joxit/docker-registry-ui/issues/70) proxy_ssl_server_name on; proxy_buffering off; proxy_ignore_headers "X-Accel-Buffering";

I use the default Docker registry container, but with Docker Registry UI.

I’m not familiar with jfrog/artifactory but I self-host a registry on my network. I use joxit/docker-registry-ui for visualization. This is just a frontend on the API provided by the docker registry. AFAIK catalog is the best way to list the images