Skip to content

Add Community Container documentation #6173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Add Community Container documentation #6173

wants to merge 1 commit into from

Conversation

docjyJ
Copy link
Collaborator

@docjyJ docjyJ commented Mar 14, 2025

No description provided.

@docjyJ docjyJ added 1. to develop Accepted and waiting to be taken care of discussion Being discussed documentation Improvements or additions to documentation labels Mar 14, 2025
@docjyJ docjyJ added this to the next milestone Mar 14, 2025
@docjyJ docjyJ marked this pull request as draft March 14, 2025 09:00
@docjyJ
Copy link
Collaborator Author

docjyJ commented Mar 14, 2025

@szaimen WDYT ?

Signed-off-by: Jean-Yves <7360784+docjyJ@users.noreply.github.com>
@szaimen
Copy link
Collaborator

szaimen commented Mar 14, 2025

@szaimen WDYT ?

Looks already really cool, thanks for this initiative! 😊

Btw, maybe we should link this doc in this section https://github.com/nextcloud/all-in-one/tree/main/community-containers#how-to-add-containers and/or put it directly into the readme file as additonal section? Not sure what the best approach would be...

| `port_number` | The port number to expose. |
| `protocol` | The protocol to use. |

### Healthcheck
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably state in the docs that the options here are not considered inside aio. Same for other things like profiles and user...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So these options need to be set in the Dockerfile of the container...

@szaimen szaimen modified the milestones: v10.9.0, next, v10.10.0 Mar 20, 2025
@szaimen szaimen modified the milestones: v10.11.0, next Apr 1, 2025
@szaimen szaimen modified the milestones: v10.12.0, next, v10.13.0 Apr 11, 2025
@szaimen szaimen modified the milestones: v10.14.0, next May 2, 2025
@szaimen szaimen modified the milestones: v10.15.0, next May 19, 2025
@docjyJ docjyJ self-assigned this May 26, 2025
@szaimen
Copy link
Collaborator

szaimen commented May 30, 2025

Hi @docjyJ any update here? :)

@szaimen szaimen modified the milestones: v11.0.0, next May 30, 2025
@docjyJ
Copy link
Collaborator Author

docjyJ commented May 30, 2025

What elements are not supported?

@szaimen
Copy link
Collaborator

szaimen commented May 30, 2025

What elements are not supported?

The healthcheck options and some other things like profiles and user are not actually forwarded to the container. See #5574 (comment) so we should make that clear in the docs that they need to be set directly in the Dockerfile of the container instead imho

@szaimen szaimen removed this from the next milestone Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Accepted and waiting to be taken care of discussion Being discussed documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants