Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Volumes are not working

Volumes are not working

Scheduled Pinned Locked Moved Solved Support
volumeslycheesyncthing
21 Posts 5 Posters 3.1k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S subtlecourage

    I have added the volume in Cloudron

    73113fbf-cb92-4ffc-9ee5-3ba7464ee808-image.png

    Its a local filesystem mount

    I have added the mount in the app Lychee and Syncthing
    3028608f-e724-4178-9d08-836119f4910f-image.png

    768f8957-2500-4757-b576-af22debb285d-image.png

    However, when I got to either apps file manager, there is no Media folder

    There is no media folder4faaabc0-c4c2-443e-96d6-d5bf519a8d78-image.png

    Any ideas?

    BrutalBirdieB Offline
    BrutalBirdieB Offline
    BrutalBirdie
    Partner
    wrote on last edited by
    #2

    @subtlecourage Because you are looking at the wrong place.

    Read carefully what the Volumes text says:

    Volumes are attached to the app's container under /media

    Your file browser is pointing at /app/data/media if you want to view the volume you have to press the 3 dots on the right (menu button) and just click your volume that is mounted.

    Or you can view the files in your terminal ls -lah /media

    Like my work? Consider donating a drink. Cheers!

    S 1 Reply Last reply
    0
    • BrutalBirdieB BrutalBirdie

      @subtlecourage Because you are looking at the wrong place.

      Read carefully what the Volumes text says:

      Volumes are attached to the app's container under /media

      Your file browser is pointing at /app/data/media if you want to view the volume you have to press the 3 dots on the right (menu button) and just click your volume that is mounted.

      Or you can view the files in your terminal ls -lah /media

      S Offline
      S Offline
      subtlecourage
      wrote on last edited by
      #3

      @brutalbirdie

      So it is located there, in the three drop down items, but I can not use the volume.

      /media/portfolio
      f72ac635-e9a7-4edb-9401-675029450ba5-image.png

      /portfolio
      018cb834-dba2-4c05-b95c-9b764e658bcd-image.png

      Error messages
      a17a0766-3cdb-4815-ab18-b975f1079194-image.png

      BrutalBirdieB 1 Reply Last reply
      0
      • S subtlecourage

        @brutalbirdie

        So it is located there, in the three drop down items, but I can not use the volume.

        /media/portfolio
        f72ac635-e9a7-4edb-9401-675029450ba5-image.png

        /portfolio
        018cb834-dba2-4c05-b95c-9b764e658bcd-image.png

        Error messages
        a17a0766-3cdb-4815-ab18-b975f1079194-image.png

        BrutalBirdieB Offline
        BrutalBirdieB Offline
        BrutalBirdie
        Partner
        wrote on last edited by
        #4

        @subtlecourage I will try to replicate your problem.

        Like my work? Consider donating a drink. Cheers!

        S 1 Reply Last reply
        1
        • BrutalBirdieB BrutalBirdie

          @subtlecourage I will try to replicate your problem.

          S Offline
          S Offline
          subtlecourage
          wrote on last edited by
          #5

          @brutalbirdie said in Volumes are not working:

          @subtlecourage I will try to replicate your problem.

          Thank you, it is appreciated.

          BrutalBirdieB 2 Replies Last reply
          0
          • S subtlecourage

            @brutalbirdie said in Volumes are not working:

            @subtlecourage I will try to replicate your problem.

            Thank you, it is appreciated.

            BrutalBirdieB Offline
            BrutalBirdieB Offline
            BrutalBirdie
            Partner
            wrote on last edited by BrutalBirdie
            #6

            @subtlecourage Which app is showing this error message?
            Since you show Lychee and Syncthing.

            If you could provide some error tracing steps what you did that would be helpful.

            Like my work? Consider donating a drink. Cheers!

            BrutalBirdieB 1 Reply Last reply
            0
            • BrutalBirdieB BrutalBirdie

              @subtlecourage Which app is showing this error message?
              Since you show Lychee and Syncthing.

              If you could provide some error tracing steps what you did that would be helpful.

              BrutalBirdieB Offline
              BrutalBirdieB Offline
              BrutalBirdie
              Partner
              wrote on last edited by BrutalBirdie
              #7

              @brutalbirdie OK its Syncthing

              Like my work? Consider donating a drink. Cheers!

              1 Reply Last reply
              0
              • S subtlecourage

                @brutalbirdie said in Volumes are not working:

                @subtlecourage I will try to replicate your problem.

                Thank you, it is appreciated.

                BrutalBirdieB Offline
                BrutalBirdieB Offline
                BrutalBirdie
                Partner
                wrote on last edited by BrutalBirdie
                #8

                @subtlecourage OK so default the volume is mounted with permissions for root.

                You can check this in the web terminal:

                ls -lah /media/
                
                root@d2ff17d2-7106-48bc-87bc-fab2342c0059:/app/code# ls -lah /media/
                total 12K
                drwxr-xr-x 1 root root 4.0K Oct  3 20:07 .
                drwxr-xr-x 1 root root 4.0K Oct  3 20:07 ..
                drwxr-xr-x 3 root root 4.0K Oct  3 20:09 portfolio
                

                But this is wrong. If you check the permissions of /app/data/

                ls -lah /app/data/
                
                rwxr-xr-x 4 cloudron cloudron 4.0K Oct  3 20:06 .
                drwxr-xr-x 1 root     root     4.0K Oct  3 20:07 ..
                drwx------ 3 cloudron cloudron 4.0K Oct  3 20:09 config
                drwxr-xr-x 2 cloudron cloudron 4.0K Oct  3 20:06 folders
                

                The user is cloudron.

                We can also check which user is running the process:

                ps uax
                
                USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
                root           1  0.1  0.0  28480 23648 pts/0    Ss+  20:17   0:00 /usr/bin/python3 /usr/bin/supervisord --configuration /etc/supervisor/supervisord.conf --nodaemon -i syncthing
                cloudron      12  0.0  0.0 725144 16408 pts/0    Sl   20:17   0:00 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                root          13  0.0  0.0  18840  6184 pts/0    S    20:17   0:00 nginx: master process /usr/sbin/nginx -c /app/code/nginx.conf
                cloudron      18  0.0  0.0  19188  3376 pts/0    S    20:17   0:00 nginx: worker process
                cloudron      19  0.0  0.0  18984  2372 pts/0    S    20:17   0:00 nginx: cache manager process
                cloudron      24  2.2  0.0 728088 49152 pts/0    SNl  20:17   0:02 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                root          39  0.0  0.0   4240  3460 pts/1    Ss   20:17   0:00 /bin/bash
                root          58  0.0  0.0   5896  2828 pts/1    R+   20:19   0:00 ps uax
                

                and the process is also running as user cloudron.

                Now you can simple change the permissions for /media/portfolio

                chown -R cloudron:cloudron /media/portfolio
                

                Then reload Syncthing (browser refresh).

                5977614c-baae-440d-bd47-27c7dcb91f99-image.png

                Now there is this warning / error hmmmm

                Like my work? Consider donating a drink. Cheers!

                BrutalBirdieB S 2 Replies Last reply
                3
                • BrutalBirdieB BrutalBirdie

                  @subtlecourage OK so default the volume is mounted with permissions for root.

                  You can check this in the web terminal:

                  ls -lah /media/
                  
                  root@d2ff17d2-7106-48bc-87bc-fab2342c0059:/app/code# ls -lah /media/
                  total 12K
                  drwxr-xr-x 1 root root 4.0K Oct  3 20:07 .
                  drwxr-xr-x 1 root root 4.0K Oct  3 20:07 ..
                  drwxr-xr-x 3 root root 4.0K Oct  3 20:09 portfolio
                  

                  But this is wrong. If you check the permissions of /app/data/

                  ls -lah /app/data/
                  
                  rwxr-xr-x 4 cloudron cloudron 4.0K Oct  3 20:06 .
                  drwxr-xr-x 1 root     root     4.0K Oct  3 20:07 ..
                  drwx------ 3 cloudron cloudron 4.0K Oct  3 20:09 config
                  drwxr-xr-x 2 cloudron cloudron 4.0K Oct  3 20:06 folders
                  

                  The user is cloudron.

                  We can also check which user is running the process:

                  ps uax
                  
                  USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
                  root           1  0.1  0.0  28480 23648 pts/0    Ss+  20:17   0:00 /usr/bin/python3 /usr/bin/supervisord --configuration /etc/supervisor/supervisord.conf --nodaemon -i syncthing
                  cloudron      12  0.0  0.0 725144 16408 pts/0    Sl   20:17   0:00 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                  root          13  0.0  0.0  18840  6184 pts/0    S    20:17   0:00 nginx: master process /usr/sbin/nginx -c /app/code/nginx.conf
                  cloudron      18  0.0  0.0  19188  3376 pts/0    S    20:17   0:00 nginx: worker process
                  cloudron      19  0.0  0.0  18984  2372 pts/0    S    20:17   0:00 nginx: cache manager process
                  cloudron      24  2.2  0.0 728088 49152 pts/0    SNl  20:17   0:02 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                  root          39  0.0  0.0   4240  3460 pts/1    Ss   20:17   0:00 /bin/bash
                  root          58  0.0  0.0   5896  2828 pts/1    R+   20:19   0:00 ps uax
                  

                  and the process is also running as user cloudron.

                  Now you can simple change the permissions for /media/portfolio

                  chown -R cloudron:cloudron /media/portfolio
                  

                  Then reload Syncthing (browser refresh).

                  5977614c-baae-440d-bd47-27c7dcb91f99-image.png

                  Now there is this warning / error hmmmm

                  BrutalBirdieB Offline
                  BrutalBirdieB Offline
                  BrutalBirdie
                  Partner
                  wrote on last edited by BrutalBirdie
                  #9

                  @brutalbirdie ok it seems I am just to impatient. But I just restarted the app and the .stfolder got created.

                  If this solved your problem please mark the little guide as the answer.

                  👋

                  Like my work? Consider donating a drink. Cheers!

                  1 Reply Last reply
                  2
                  • girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #10

                    Also, lychee has it's own "database" for files. It cannot use an existing directory. So, you cannot really use the volume feature to mount existing files and display them using lychee. You can to "upload" the files into lychee. See https://github.com/electerious/Lychee/blob/master/docs/FAQ.md#can-i-use-my-existing-folder-structure

                    1 Reply Last reply
                    0
                    • BrutalBirdieB BrutalBirdie

                      @subtlecourage OK so default the volume is mounted with permissions for root.

                      You can check this in the web terminal:

                      ls -lah /media/
                      
                      root@d2ff17d2-7106-48bc-87bc-fab2342c0059:/app/code# ls -lah /media/
                      total 12K
                      drwxr-xr-x 1 root root 4.0K Oct  3 20:07 .
                      drwxr-xr-x 1 root root 4.0K Oct  3 20:07 ..
                      drwxr-xr-x 3 root root 4.0K Oct  3 20:09 portfolio
                      

                      But this is wrong. If you check the permissions of /app/data/

                      ls -lah /app/data/
                      
                      rwxr-xr-x 4 cloudron cloudron 4.0K Oct  3 20:06 .
                      drwxr-xr-x 1 root     root     4.0K Oct  3 20:07 ..
                      drwx------ 3 cloudron cloudron 4.0K Oct  3 20:09 config
                      drwxr-xr-x 2 cloudron cloudron 4.0K Oct  3 20:06 folders
                      

                      The user is cloudron.

                      We can also check which user is running the process:

                      ps uax
                      
                      USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
                      root           1  0.1  0.0  28480 23648 pts/0    Ss+  20:17   0:00 /usr/bin/python3 /usr/bin/supervisord --configuration /etc/supervisor/supervisord.conf --nodaemon -i syncthing
                      cloudron      12  0.0  0.0 725144 16408 pts/0    Sl   20:17   0:00 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                      root          13  0.0  0.0  18840  6184 pts/0    S    20:17   0:00 nginx: master process /usr/sbin/nginx -c /app/code/nginx.conf
                      cloudron      18  0.0  0.0  19188  3376 pts/0    S    20:17   0:00 nginx: worker process
                      cloudron      19  0.0  0.0  18984  2372 pts/0    S    20:17   0:00 nginx: cache manager process
                      cloudron      24  2.2  0.0 728088 49152 pts/0    SNl  20:17   0:02 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                      root          39  0.0  0.0   4240  3460 pts/1    Ss   20:17   0:00 /bin/bash
                      root          58  0.0  0.0   5896  2828 pts/1    R+   20:19   0:00 ps uax
                      

                      and the process is also running as user cloudron.

                      Now you can simple change the permissions for /media/portfolio

                      chown -R cloudron:cloudron /media/portfolio
                      

                      Then reload Syncthing (browser refresh).

                      5977614c-baae-440d-bd47-27c7dcb91f99-image.png

                      Now there is this warning / error hmmmm

                      S Offline
                      S Offline
                      subtlecourage
                      wrote on last edited by
                      #11

                      @brutalbirdie said in Volumes are not working:

                      @subtlecourage OK so default the volume is mounted with permissions for root.

                      You can check this in the web terminal:

                      ls -lah /media/
                      
                      root@d2ff17d2-7106-48bc-87bc-fab2342c0059:/app/code# ls -lah /media/
                      total 12K
                      drwxr-xr-x 1 root root 4.0K Oct  3 20:07 .
                      drwxr-xr-x 1 root root 4.0K Oct  3 20:07 ..
                      drwxr-xr-x 3 root root 4.0K Oct  3 20:09 portfolio
                      

                      But this is wrong. If you check the permissions of /app/data/

                      ls -lah /app/data/
                      
                      rwxr-xr-x 4 cloudron cloudron 4.0K Oct  3 20:06 .
                      drwxr-xr-x 1 root     root     4.0K Oct  3 20:07 ..
                      drwx------ 3 cloudron cloudron 4.0K Oct  3 20:09 config
                      drwxr-xr-x 2 cloudron cloudron 4.0K Oct  3 20:06 folders
                      

                      The user is cloudron.

                      We can also check which user is running the process:

                      ps uax
                      
                      USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
                      root           1  0.1  0.0  28480 23648 pts/0    Ss+  20:17   0:00 /usr/bin/python3 /usr/bin/supervisord --configuration /etc/supervisor/supervisord.conf --nodaemon -i syncthing
                      cloudron      12  0.0  0.0 725144 16408 pts/0    Sl   20:17   0:00 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                      root          13  0.0  0.0  18840  6184 pts/0    S    20:17   0:00 nginx: master process /usr/sbin/nginx -c /app/code/nginx.conf
                      cloudron      18  0.0  0.0  19188  3376 pts/0    S    20:17   0:00 nginx: worker process
                      cloudron      19  0.0  0.0  18984  2372 pts/0    S    20:17   0:00 nginx: cache manager process
                      cloudron      24  2.2  0.0 728088 49152 pts/0    SNl  20:17   0:02 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                      root          39  0.0  0.0   4240  3460 pts/1    Ss   20:17   0:00 /bin/bash
                      root          58  0.0  0.0   5896  2828 pts/1    R+   20:19   0:00 ps uax
                      

                      and the process is also running as user cloudron.

                      Now you can simple change the permissions for /media/portfolio

                      chown -R cloudron:cloudron /media/portfolio
                      

                      Then reload Syncthing (browser refresh).

                      5977614c-baae-440d-bd47-27c7dcb91f99-image.png

                      Now there is this warning / error hmmmm

                      Sadly this did not solve my problem

                      I have followed your guide step by step and I get d7a84845-28a7-453a-b069-cecd25f5b8e1-image.png

                      I have ran your commands, dc85ce85-7c68-4c33-915c-9ad2711b3575-image.png

                      and I have restarted the app, twice after running those.

                      But it still has not done anything
                      4b2d6eaa-4715-44ca-a1cf-9d1e4923d290-image.png

                      BrutalBirdieB 1 Reply Last reply
                      0
                      • S subtlecourage

                        @brutalbirdie said in Volumes are not working:

                        @subtlecourage OK so default the volume is mounted with permissions for root.

                        You can check this in the web terminal:

                        ls -lah /media/
                        
                        root@d2ff17d2-7106-48bc-87bc-fab2342c0059:/app/code# ls -lah /media/
                        total 12K
                        drwxr-xr-x 1 root root 4.0K Oct  3 20:07 .
                        drwxr-xr-x 1 root root 4.0K Oct  3 20:07 ..
                        drwxr-xr-x 3 root root 4.0K Oct  3 20:09 portfolio
                        

                        But this is wrong. If you check the permissions of /app/data/

                        ls -lah /app/data/
                        
                        rwxr-xr-x 4 cloudron cloudron 4.0K Oct  3 20:06 .
                        drwxr-xr-x 1 root     root     4.0K Oct  3 20:07 ..
                        drwx------ 3 cloudron cloudron 4.0K Oct  3 20:09 config
                        drwxr-xr-x 2 cloudron cloudron 4.0K Oct  3 20:06 folders
                        

                        The user is cloudron.

                        We can also check which user is running the process:

                        ps uax
                        
                        USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
                        root           1  0.1  0.0  28480 23648 pts/0    Ss+  20:17   0:00 /usr/bin/python3 /usr/bin/supervisord --configuration /etc/supervisor/supervisord.conf --nodaemon -i syncthing
                        cloudron      12  0.0  0.0 725144 16408 pts/0    Sl   20:17   0:00 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                        root          13  0.0  0.0  18840  6184 pts/0    S    20:17   0:00 nginx: master process /usr/sbin/nginx -c /app/code/nginx.conf
                        cloudron      18  0.0  0.0  19188  3376 pts/0    S    20:17   0:00 nginx: worker process
                        cloudron      19  0.0  0.0  18984  2372 pts/0    S    20:17   0:00 nginx: cache manager process
                        cloudron      24  2.2  0.0 728088 49152 pts/0    SNl  20:17   0:02 /app/code/syncthing -gui-address=127.0.0.1:3000 -home=/app/data/config -no-browser -auditfile=-
                        root          39  0.0  0.0   4240  3460 pts/1    Ss   20:17   0:00 /bin/bash
                        root          58  0.0  0.0   5896  2828 pts/1    R+   20:19   0:00 ps uax
                        

                        and the process is also running as user cloudron.

                        Now you can simple change the permissions for /media/portfolio

                        chown -R cloudron:cloudron /media/portfolio
                        

                        Then reload Syncthing (browser refresh).

                        5977614c-baae-440d-bd47-27c7dcb91f99-image.png

                        Now there is this warning / error hmmmm

                        Sadly this did not solve my problem

                        I have followed your guide step by step and I get d7a84845-28a7-453a-b069-cecd25f5b8e1-image.png

                        I have ran your commands, dc85ce85-7c68-4c33-915c-9ad2711b3575-image.png

                        and I have restarted the app, twice after running those.

                        But it still has not done anything
                        4b2d6eaa-4715-44ca-a1cf-9d1e4923d290-image.png

                        BrutalBirdieB Offline
                        BrutalBirdieB Offline
                        BrutalBirdie
                        Partner
                        wrote on last edited by BrutalBirdie
                        #12

                        @subtlecourage do you know that linux is case sensitive?

                        You point to /media/Portfolio but from your ls -lah on /media the folder is called portfolio.
                        Also the error folder path missing is kind of a dead giveaway adding to the Failed to crate folder implying the folder does not exist hence the software tries to crate it.

                        Like my work? Consider donating a drink. Cheers!

                        S 1 Reply Last reply
                        2
                        • BrutalBirdieB BrutalBirdie

                          @subtlecourage do you know that linux is case sensitive?

                          You point to /media/Portfolio but from your ls -lah on /media the folder is called portfolio.
                          Also the error folder path missing is kind of a dead giveaway adding to the Failed to crate folder implying the folder does not exist hence the software tries to crate it.

                          S Offline
                          S Offline
                          subtlecourage
                          wrote on last edited by
                          #13

                          @brutalbirdie

                          Ha, always the simplest solution. Thank you.

                          BrutalBirdieB 1 Reply Last reply
                          1
                          • S subtlecourage

                            @brutalbirdie

                            Ha, always the simplest solution. Thank you.

                            BrutalBirdieB Offline
                            BrutalBirdieB Offline
                            BrutalBirdie
                            Partner
                            wrote on last edited by
                            #14

                            @subtlecourage so all sorted out? Now working as intended?

                            Like my work? Consider donating a drink. Cheers!

                            S 1 Reply Last reply
                            0
                            • BrutalBirdieB BrutalBirdie

                              @subtlecourage so all sorted out? Now working as intended?

                              S Offline
                              S Offline
                              subtlecourage
                              wrote on last edited by
                              #15

                              @brutalbirdie Yup, all sorted and working as intended for now.
                              I have upvoted your comment above. Thank you.

                              1 Reply Last reply
                              1
                              • S Offline
                                S Offline
                                SamGreenwood
                                wrote on last edited by
                                #16

                                I'm having a similar issue and, I think that the problem could be that for some reason the app can't access the mounted volume even though it's connected (to Cloudron) properly.

                                BrutalBirdieB 1 Reply Last reply
                                0
                                • S SamGreenwood

                                  I'm having a similar issue and, I think that the problem could be that for some reason the app can't access the mounted volume even though it's connected (to Cloudron) properly.

                                  BrutalBirdieB Offline
                                  BrutalBirdieB Offline
                                  BrutalBirdie
                                  Partner
                                  wrote on last edited by
                                  #17

                                  @SamGreenwood
                                  Then you should read the whole topic from the start 😉
                                  I also described a permission issue and how to fix it.

                                  TL;DR
                                  By default the mounted volume and folder are with root permission.
                                  These need to be changed to cloudron.

                                  Like my work? Consider donating a drink. Cheers!

                                  S 1 Reply Last reply
                                  0
                                  • BrutalBirdieB BrutalBirdie

                                    @SamGreenwood
                                    Then you should read the whole topic from the start 😉
                                    I also described a permission issue and how to fix it.

                                    TL;DR
                                    By default the mounted volume and folder are with root permission.
                                    These need to be changed to cloudron.

                                    S Offline
                                    S Offline
                                    SamGreenwood
                                    wrote on last edited by
                                    #18

                                    I got it working

                                    BrutalBirdieB 1 Reply Last reply
                                    0
                                    • S SamGreenwood

                                      I got it working

                                      BrutalBirdieB Offline
                                      BrutalBirdieB Offline
                                      BrutalBirdie
                                      Partner
                                      wrote on last edited by
                                      #19

                                      @SamGreenwood That's nice to hear, but always share / link the solution!

                                      Just remember how often you searched for a solution and the answer was simply "I solved it" END!

                                      Don't be that guy! Document Solutions!

                                      Like my work? Consider donating a drink. Cheers!

                                      benborgesB 1 Reply Last reply
                                      2
                                      • BrutalBirdieB BrutalBirdie

                                        @SamGreenwood That's nice to hear, but always share / link the solution!

                                        Just remember how often you searched for a solution and the answer was simply "I solved it" END!

                                        Don't be that guy! Document Solutions!

                                        benborgesB Offline
                                        benborgesB Offline
                                        benborges
                                        wrote on last edited by benborges
                                        #20

                                        moved to nocodb section

                                        BenB

                                        1 Reply Last reply
                                        0
                                        • girishG Offline
                                          girishG Offline
                                          girish
                                          Staff
                                          wrote on last edited by
                                          #21

                                          https://forum.cloudron.io/topic/7619/filesystem-mount-inside-container for others to follow along.

                                          1 Reply Last reply
                                          1
                                          • T THI_Staff referenced this topic on
                                          • benborgesB benborges referenced this topic on
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Bookmarks
                                          • Search