think about a solution to add your own containers.json files

[szaimen]

Required:

• add docs add docs on the community-containers feature #3431
• additionally should additoonal containers alway rely on the apache container so that they get started at all (if display_name not empty, add to the list) merge containers.json and make sure they depend on the apache container #3425
• merge services array with https://www.php.net/manual/en/function.array-merge-recursive.php? merge containers.json and make sure they depend on the apache container #3425
• allow to enable apps by specifying its name via variable, then choose file automatically allow to specify AIO_COMMUNITY_CONTAINERS #3424
• community containers must be bundled in AIO during build time. By doing so we make sure that containers.json is always valid allow to specify AIO_COMMUNITY_CONTAINERS #3424
• Add minlenght to json schema strings: https://stackoverflow.com/a/53733250 add patterns to containers-schema #2429
• Also add other types or regex? https://json-schema.org/understanding-json-schema/index.html# add patterns to containers-schema #2429
• remove

  all-in-one/php/composer.json

  Line 20 in 3e08843

  "justinrainbow/json-schema": "^5.2"

  again since we test with CI and bundle things remove justinrainbow/json-schema again #3417
• as a follow-up, add some documentation on this: e.g. where containers need to get deployed (on docker hub), which are tags that are needed (maybe also link to some giithub actions), what is currently possible regarding env variables, etc. in best case should you run docker rootless and obviously only add definitions of trusted people
• merge expose and internal_port of containeers definition or rename internal_port to network_mode not needed since expose is not needed for AIO to work. Only an internal thing for kubernetes to work. So still only internal_port is used for checking the availability
• maybe even allow to run docker exec commands that get executed after all containers are running. (Disable setting on-click instance settings) allow to define nextcloud_exec_commands in containers definition #2454
• for reverse proxy we need to provide a way to expand the conf. Could probably use the caddy import statement for this: https://caddyserver.com/docs/caddyfile/directives/import. For the template itself should be added to an additional volume that could be mounted into the apache container and mounted by the additional container with the restriction that only subdirectories are supported. For anything that needs a domain should probably rather a reverse proxy get used allow to add imports to the caddy file #2457
• add some docs for the feature above
• add docs for host mode container feature
• We could add a way to allow to run a reverse proxy from the custom containers.json (hostmode would be needed then; this would allow much more customization) (by setting internal_port to "host"
• add documentation on global variables and how to use them.
• allow to add devices to container.json
• allow to define CapAdd in containers.json fix set_memory for imaginary and move cap_add to containers.json #2113
• allow to enable securityopt: apparmor=undefined add apparmor_unconinfed to containers definition #2432
• validate json before merging it with default containers.json: https://github.com/justinrainbow/json-schema validate json against json schema #2611
• allow to define if a volume gets included in backup and restore e.g. via include_in_backup_and_restore allow to include volumes in backup and restore #2455
• Multiarch Docker #490 (comment)
• add profiles and networks to containers definition so that it can be removed form update-yaml.sh add profiles and networks to container-schema.json #2631
• add image_tag to definition-schema in order to allow to pin the container tag and not rely on the chosen channel. Also needs to be used for starting container and update check, etc. add image_tag to containers definition #3191
• also use image_tag in containers.json for better testing? Would need a new variable then so that it gets subsituted automatically. In that case image_tag should be required require image_tag and add %AIO_CHANNEL% variable #3314

Follow-ups:

• think about instance restore: should teh backup container run twice in a row to restore the setting first and then start the correct restore?
• Only add
  • vaultwarden
  • plex
  • smbserver
  • caddy with geoblocking
  • disk monitoring? (better do from host)
  • pihole
  • pivpn (use fritzbox)
  • remotedesktop
  • fail2ban community-containers - add fail2ban as example container for testing purposes #2637
• instead of modifying container to put a caddy import into place, should there be an option to modify a subpath that is automatically forwarded to the correct container in a subpath available on the nextcloud domain? containers definition - allow to define caddy_routes #3192 (maybe also use that in the containers but must also work without)
• allow to define if a secret gets shown in the aio interface and also allow to add a description for a secret and also allow to add a description of what the token does
• allow to set not defined environmental variables from the aio interface: by providing an input field and regex and maybe even description).
• allow to define custom cronjobs

PRs:

• rename values of containers definition to match docker-compose values #1595
• allow to add container to host network #1597
• allow to hide containers from the interface via display_name #1598
• refactor containerports #1599
• substitute volume variables in dockeractionmanager #1603
• improve containeers schema #1604
• refactor containerports #1635
• rename volume name to source and volume location to destination #1637
• allow to add the /dev/dri device into the container and refactor devices #1659
• add a more generous solution to starting containers while backup stil… #2029
• fix set_memory for imaginary and move cap_add to containers.json #2113
• add patterns to containers-schema #2429
• add apparmor_unconinfed to containers definition #2432
• community-containers - add fail2ban as example container for testing purposes #2637

[szaimen]

Required things are done. Follow-ups in #3432

[szaimen]

This is now released with v7.4.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel