Posts by jaytee1414

Quote from gderf

You may have fundamental misunderstandings of various key concepts, including but not limited to users, groups, filesystem permissions and ownerships, and docker basic principles. This can be aggravated by viewing online videos and howtos, and parroting what you find there into your system without really understanding what it is you are actually doing. Most if not all of those videos and howtos are making silent assumptions that these basic concepts are already part of your experience base. Are they?

We're here to help, but to get the best start we need how much of what you are going to need to know you already know.

I do know my knowledge is limited and I'm learning as I go and the fact that I follow the videos but it's not going as smooth as their videos complicates me...

My docker related items are installed on my external direct of my RPi4 with the directory of -> /srv/dev-disk-by-label-Data/appdata which is the share folder specific for my docker. This share folder on OMV gui is set to the permission of everyone have read/write access

Going through the folder on my mac shows portainer_data folder under volumes and also docker containers / images under the folder. (not changing anything just looking around. But to look around it it required me to change the folder permission to 777 (i know 777 is not secure at all so I changed to 755), which makes my first problem because it seems to also cause the web gui access of portainer to not work and I assume that OMV should provide enough permission at an automatic level that allows basic stuff such as portainer to work?

This leads to the problem of when I install other dockers such as Letsencrypt, it seems to not be able to read it's own files or internally communicated with itself without modifying the folder permission to 755. I gave a pgid=100, which is the user group access for the docker, which I assume is enough and should not require root level access?

My question is why when portainer pulls a new image and creating the docker's own files (/config) would change the permission. I know that some "software" would lock or hide files hoping users to not be able to alter and corrupt the "software". But my case is causing my docker to not be able to work even at fresh install like my Mariadb that I'm still working on..

Quote from olduser

- Docker is the name of the software that runs containers. (ie. VirtualBox)

- Containers are what the docker software runs. (ie. sandboxes)

Are you using Docker to run a container named "docker" in recursion? If not, that "docker" directory isn't of consequence to you at this time.

-v "/home/$USER/apps/specific_dir:/config"

The above will (or will attempt) to mount/shadow the /config directory inside of *ANY* container to your local filesystem at /home/$USER/apps/specific_dir.

As far as the excessive deleting and reinstalling goes...

When docker pulls down an image from docker hub or wherever, it pulls down an image, *NOT* a container. Think of it as a mold waiting for you to fill in and bake, you'll keep the mold as is but you might keep or throw away what is baked in it.

Actually, let me try an hit that part home again... You use a torrent client right? Well you don't download your files into your torrent program's directory right? You don't delete you're torrent client every time you want to delete your "movies" right?

Unless you're editing or creating your own image, *NOT* container, then the most you'll ever need to delete is the "specific_dir" in the above example.

Ultimately, you shouldn't have to use rm or at least you don't want to, but if you do you'll be using:

rm -rf "/home/$USER/apps/specific_dir"

or

rm -rf "/home/$USER/apps/*/"

Again though, you don't want to do that unless you have to.

P.S. Years ago, years... every Linux install you came across had a "Chapter 1" with how to setup lilo, how to partition, where to put mounts, where to store modules, etc... Ultimately, people became tired of it and just skipped Chapter 1 and looked for specifics. However, in your case, you need to read "Chapter 1".

Display More

I think my problem is more fundamentally wrong? This docker file is the actual install of dockers when you press install on OMV gui in the OMV extra -> Docker page. The problem i am having is the files denies permissions causing problem like if I don't manually change it's permission, after restarting, even portainer web gui cannot be accessed. When new dockers are installed, various files in their config behave similarly like letsencrypt which you need to change config files to make it work and again require chmod -R 755 or just to make it work. I'm not sure what is wrong there. I give PUID 1000 and PGID 100 to the container deploy but doesnt seem to help the situation.

My fresh install of Mariadb stuck with the following logs during startup

[cont-init.d] 10-adduser: exited 0.,
[cont-init.d] 30-config: executing... ,
[cont-init.d] 30-config: exited 0.,
[cont-init.d] 40-initialise-db: executing... ,
[cont-init.d] 40-initialise-db: exited 0.,
[cont-init.d] 99-custom-scripts: executing... ,
[custom-init] no custom files found exiting...,
[cont-init.d] 99-custom-scripts: exited 0.,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
200814 19:20:44 mysqld_safe Logging to syslog.,
200814 19:20:44 mysqld_safe Starting mysqld daemon with databases from /config/databases,

Anyone have the same problem? I deleted and reinstalled the docker with removing the image and everything still spit the same code....

Other places say is corrupted database but no matter how i reinstall i still get the same output

Setup:

RPi 4 OMV5.5.8-1

Portainer 19.03.12

Quote from Morlan

Is it a custom bridge network or the default?

Actually the problem was the editing of conf files and config.php failed with mac textedit fixed with using textmate

Quote from shishio

Duckdns address is wrong.

It should be: subdomain.duckdns.org

example: mycloud.duckdns.org

nextcloud.subdomain.conf:

server_name nextcloud.*; ---> server_name mycloud.*;

config.php nextcloud:

'trusted_proxies' => ['letsencrypt'],

'overwrite.cli.url' => 'https://mycloud.duckdns.org/',

'overwritehost' => 'mycloud.duckdns.org',

'overwriteprotocol' => 'https',

array (

0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.

1 => 'mycloud.duckdns.org',

restart nextcloud and letsencrypt containers.

Display More

I reinstalled omv 5 started all over again but still end up the same situation

subdomain -> mycloud

my nextcloud.subdomain.conf
server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name mycloud.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app nextcloud;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 1024m;
    }
}

my config.php
<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',

'trusted_proxies' => ['letsencrypt'],
'overwrite.cli.url' => 'https://mycloud.duckdns.org/',
'overwritehost' => 'mycloud.duckdns.org',
'overwriteprotocol' => 'https',

array (
0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
1 => 'mycloud.duckdns.org',
),

);

mariadb, letsencrypt, nextcloud and duckdns in the same bridge, port forwarding done... anything else i should try?

Hi is anyone still viewing this post.... I reinstalled omv but the problem still occurs... I installed docker via omv extras but the docker dir become inaccessible, which my account that i connect with has highest priority while all permission is basically allowed on this appdata share... someone tell me what is the problem?

">

This makes portainer inaccessible via web gui as well because after installing portainer its blocked by the permission, so stuff just won't load

#I tried give the dir permission via ssh with
sudo chmod 777 docker
#still don't work

Hi I have been trying to get my omv 5 on raspberry pi with docker working... I deleted everything related to docker because my previous stuff just seems to work but now I can't even get docker installed

">

Please help, thanks in advance

Quote from seanmccabe

I've never had an issue with Docker messing with the permissions, usually just a case on ensuring when you are setting up the container you are providing it with an PGID and PUID to use that has appropriate permissions on the folders it is allowed to access.

If the contaner makes files or folders, then that way they are created with the appropriate permissions.

I usually make a user called docker, add it to a group called docker, but also add it to the users group so that any files created by the docker user are accessible via any user in the users group and vice versa

      - PUID=1000
      - PGID=100

This is the PUID and PGID that I set when I installed the dockers that I want. I am not sure what the problem is but I have deleted all docker related files and trying to restart once again and see what settings might have messed up such as portainer install. I'll see the docker user and group thing but not sure if i know what I'm doing iwth user group.. Should I give all permission for the docker user?

Hi, I have been encountering a problem with my share folder permission after installing new docker. I had problems with using Nextcloud and Let's encrypt previously so I decided to delete everything on my docker share and start over and now its messing up with the permission. I have to go and do reset permission on the folder even when it it set to everyone allowed. It seems the reset perm is also struggling? where it takes very long time but normally it is very fast..

the folder have permission of the following when check with ls -l

drwxrwsrwx   3 root users  4096

Is there a way to install docker without messing up the permissions?

System:

Raspberry Pi 4 OMV 5-5-5.1

Portainer 19.03.12

Any info can be requested to help

Quote from shishio

Hi,

You should check the following:

- The nextcloud config.php configuration is correct.

- Restart nextcloud container.

- The letsencrypt container is called "letsencrypt".

- Restart the letsencrypt container after renaming the nextcloud.subdomain.conf.sample file.

- The mariadb, letsencrypt, nextcloud and duckdns containers on the same custom brigde network.

Display More

I added duckdns to the bridge network, but it didn't work, spellings of containers seems to be fine.

This is my config.php for nextcloud i added a few lines according to nextcloud.subdomain.conf thing but not sure if would help or harm. (original and edited still doesnt lead to it working tho...:

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'ocf2cw23tbhi',

array (
 0 => '192.168.1.62:444',
 1 => 'nextcloud.mysubdomain.duckdns.org',
),

'trusted_proxies' => ['letsencrypt'],
'overwrite.cli.url' => 'https://nextcloud.mysubdomain.duckdns.org',
'overwritehost' => 'nextcloud.mysubdomain.duckdns.org',
'overwriteprotocol' => 'https',

);
#"mysubdomain" is replacement of the real thing to whom may concern

Anything i can try? like time zone or anything.... just feel like letsencrypt is the thing blocking the external communication to the nextcloud thing, ports are forwarded

Hi everyone, I have followed @TechnoDadLife's youtube video on installing Nextcloud, Let's encrypt and mariadb with via docker, which didn't go like his video (https://www.youtube.com/watch?v=4HPXGKfFibc) My problem is constantly reaching this ">

I tried to connect to the local ip with 192.168.1.XX:443 or 192.168.1.XX:82 but have no success just to get to the setup page of Nextcloud and nextcloud.mysubdomain.duckdns.org will bring me to the same page. So I would like to see if anyone have the same issue and had a solution to this problem.

My configuration is OMV 5.5.5-1 on raspberry pi 4 4gb.

My nextcloud.subdomain.conf file is set as the following:

# make sure that your dns has a cname set for nextcloud
# assuming this container is called "letsencrypt", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
#  'trusted_proxies' => ['letsencrypt'],
#  'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',
#  'overwritehost' => 'nextcloud.your-domain.com',
#  'overwriteprotocol' => 'https',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
#  array (
#    0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
#    1 => 'nextcloud.your-domain.com',
#  ),

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name nextcloud.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app nextcloud;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_max_temp_file_size 2048;
    }
}

If you like anymore information that can help, please state it in a comment and I'll post it. Thanks in advance

Update: I am able to get to the configure page by adding a port for NextCloud 444:443 in Portainer. Seems like the problem is Letsencrypt not connecting towards Nextcloud and I hope someone can help me figure it out