Repository navigation
Suggest an application for the OCI catalog #440
Replies: 7 comments 7 replies
|
Application Name: AceStream HTTP Proxy Container Registry: ghcr.io/martinbjeldbak/acestream-http-proxy Thanks in advance (media category added) |
|
Application: CrossWatch Anything it needs: Just made a custom installation using the oficial compose (adjusting the TZ), it worked for me. Thanks! |
|
Application: Free Games Claimer Remaster Anything it needs: Successfully installed and tested using OCI Manager Apps (beta), running as an unprivileged LXC without Docker. Tested resources: 2 vCPU, 4 GB RAM, 16 GB rootfs, 8 GB persistent storage and 1 GB The Compose enables all 14 supported integrations, with optional credentials and TOTP secrets entered securely during installation. Chrome, noVNC (port 7080), authentication and automatic claiming are working correctly. Persistent data and credentials are preserved across updates. Note: The included Compose leaves VNC authentication disabled, as my installation is only accessible on a trusted private network. Set Thanks! |
|
Application: MDBListarr Image: Where it is published:
Category: *Arr Suite Compose file: services:
mdblistarr:
container_name: mdblistarr
image: linaspurinis/mdblistarr:2.5.0
ports:
- "5353:5353"
environment:
- PORT=5353
- TZ=Europe/Madrid
- CSRF_TRUSTED_ORIGINS= # optional
- ALLOWED_HOSTS= # optional
volumes:
- ./mdblistarr-data:/usr/src/db/
restart: unless-stoppedAnything it needs: Successfully installed and tested using ProxMenux OCI Manager's custom Compose importer, running as a native unprivileged LXC without Docker. Tested configuration:
For reverse proxy access, configure The application is working reliably in my initial tests. |
|
Buenos días como se puede utilizar dos servicio que vienen integrado en un solo docker compose y el mismo no me aparece en el catalogo de imágenes OCI por llamarlo de alguna manera. GRACIAS https://github.com/timothepoznanski/poznote/blob/main/docker-compose.yml |
|
Application: Cloudreve Image: Where it is published:
Category: Cloud Storage / File Management Compose file: services:
cloudreve:
image: cloudreve/cloudreve:v4
container_name: cloudreve
restart: unless-stopped
ports:
- "5212:5212"
- "6888:6888"
- "6888:6888/udp"
volumes:
- ./cloudreve-data:/cloudreve/dataAnything it needs: Cloudreve is a self-hosted file management and cloud storage platform supporting local storage, S3-compatible storage, OneDrive and other providers. It provides WebDAV, multi-user access, file sharing, resumable uploads and online file previews. The configuration above uses Cloudreve's single-container deployment. For a production installation with PostgreSQL and Redis, the official deployment also provides a Docker Compose stack with separate database and cache services. Ports:
Persistent storage is required for configuration, application data and related files. I would appreciate having Cloudreve added to the ProxMenux OCI catalog so it can be installed and managed as a native Proxmox LXC without Docker. Thanks! |
|
Application: Scanopy Image:
Where it is published:
Category: Networking / Network Discovery / Infrastructure Documentation Compose file: The official Compose configuration is recommended because Scanopy requires a server, PostgreSQL database, and scanning daemon. It includes the required network access and persistent storage configuration. Use the official file for the complete deployment: Anything it needs: Scanopy is a self-hosted network discovery and documentation platform that automatically generates and updates network diagrams. It provides physical (Layer 2), logical (Layer 3), workload, and application dependency views. Key features include:
Deployment requirements and considerations:
For the ProxMenux OCI catalog, it would be especially useful to provide a native LXC deployment that preserves Scanopy's network discovery capabilities without requiring Docker. The daemon's host-networking and privilege requirements should be handled explicitly, since they are essential to reliable network discovery. The project provides a free Community Edition under the AGPL-3.0 license, as well as commercial self-hosted editions. I would appreciate having Scanopy added to the ProxMenux OCI catalog. It would be a valuable tool for Proxmox users who want automatically maintained network documentation and infrastructure visibility. Thank you! |
Uh oh!
There was an error while loading. Please reload this page.
Title: Suggest an application for the OCI catalog
Hi everyone,
OCI manager Apps installs applications from their official container images as native Proxmox LXC containers, without Docker. It arrived with the 1.2.6.2 beta and a catalog of 334 applications, and I'd like it to grow with the ones you actually use.
This thread is the place for that. There are four ways to take part, from the quickest to the most involved.
1. Suggest an application
If you use a Docker image that is not in the catalog, leave a comment with:
2. Try it yourself
You don't have to wait for the catalog. In OCI manager Apps, choose Install an image that is not in the catalog and paste its Compose file, a
docker runline or just the image reference. ProxMenux shows what it understood and what it could not translate before creating anything.If it works, tell us here what you pasted and whether you had to change something.
3. Write its oci-compose
Some applications need more than a Compose file can say: a question with its own text, a password generated during the installation, a GPU profile, a check of the first start. That is written in an oci-compose, the file ProxMenux installs an application from.
You write only what you decide (the image, its ports, variables and volumes) and ProxMenux completes the rest. The same menu option reads the file, tells you which field is wrong if there is an error, and installs it as you wrote it, so you can test and adjust.
The format is explained block by block in the README of the OCI engine, with two complete examples: Jellyfin with GPU and Duplicati with generated passwords. Attach the file that worked for you and I'll add the application from it.
4. Validate an application of the catalog
Applications tested for real show a ✓ in the installer, with the name of who tested them. The list and the steps are in oci/VALIDATION.md.
A test is simple: install the application, check that it does what it should, restart it, update it and remove it, and say which image and which options you used. For now, post the result as a comment here. With version 1.2.7 there will be a form that records it by itself once a reviewer confirms it.
A report that something does not work is just as useful as one that it does.
Thanks to everyone taking part—whether you suggest an application, test an installation, share a recipe or report a problem. Every contribution helps make the catalog more useful and reliable for all of us!
All reactions