Feat: fix nextcloud imaginary container failing issue

nextcloud/nextcloud.pod

@@ -4,8 +4,8 @@ Description=Nextcloud Pod
 [Pod]
 PodName=nextcloud
 Volume=%h/podman/nextcloud/.socket:/tmp/docker
-Network=host
 
 # to satisfy nextcloud bitch permissions problems
 UIDMap=1000:0:1
 UIDMap=0:1:1000
+UIDMap=65534:65534:1

nextcloud/nextcloud_imaginary.container

@@ -2,7 +2,7 @@
 Description=Nextcloud Imaginary Container
 
 [Container]
-Network=host
+Pod=nextcloud.pod
 ContainerName=nextcloud_imaginary
 Image=ghcr.io/nextcloud-releases/aio-imaginary
 Exec=-enable-url-source -cors

nextcloud/readme.md

@@ -1,18 +1,6 @@
 # Nextcloud
 
-The nextcloud image used is actually from linuxserver.io.
+The nextcloud image is from official nextcloud docker image.
 
 ## Major Problem
-- The fpm is unable to run as root i.e. you cannot do puid and pgid to 0 and call it a day, it won't work.
+All Resolved :)
-    - To get Around it, you have to do uidmap. Either on container level, or on pod level if doing pod (as most of us do)
-        ```ini
-            UIDMap=${PUID}:0:1
-            UIDMap=0:1:${PUID}
-        ```
-
-- Nextcloud Imaginary unable to start when this UIDMap is set on pod level, in which Imaginary is also configured.
-    - To get around with that, set this in the Imaginary.container file
-        ```ini
-            UserNS=auto
-        ```
-