How to access appdata-Folder (and subfolders) from Windows through SMB

Dear all,

I would like to access the appdata-Folder (and its sub-Folders) from Windows through SMB.

Unfortunately if i create an SMB-share and grant rights for my normal user I have got errors that I don`t have permission to access this folder.

I also tried connecting using the special appdata-User as well; unfortunately still getting errors "no permission to access".

Best regards,

MacGyver

I want to use "Tempest-EPG"-Docker-Container:

GitHub - K-vanc/Tempest-EPG-Generator: The fastest XMLTV formatted EPG Generator with GUI and the lowest memory usage

The fastest XMLTV formatted EPG Generator with GUI and the lowest memory usage - K-vanc/Tempest-EPG-Generator

github.com

---
version: "2.1"
services:
  tempest_epg:
    image: kvanc/tempest_epg:latest
    container_name: tempest_epg
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    volumes:
      - ./config/:/var/www/html/tempest_config/
    ports:
      - 8095:8095
    restart: unless-stopped

Inside the "tempest_config"-Folder there will be a "site_config"-Folder to which I must "upload" a config-file.

Additionally I will also need to link a personal "php.ini" file like in this example

/your/local/folder/php-user.ini:/etc/php82/conf.d/custom.ini

How could I do that; if not through SMB?

alexicon I have also the appdata-Folder on my MD-Raid5 I have had quite some problems locating the actual file system.

Found it yesterday through /etc/fstab on /srv/dev-disk-by-uuid-8b6b6ae4-384d-49c0-9df0-18f8320ada0d/.

Unfortunately it seems that I run in permission issues by my docker file "tempest_epg".

Normally that very script should generate files and (sub-)folder once to container is uped and/or PHP script is used.

If I use Docker for Windows and/or just a normal plain Webhosting-Package (then using only the standalone PHP file "tempest.php") it does exactly that an generates the follwing files and folders:

- cookies

- epg

- log

- site_config

- temp

- tempest.config.xml

Unfortunately on OMV it does not create that verry (sub-)folders and files for whatever reasson.

I also tried using it without the Global Environment Variables PUID, PGID.

Unfortunately it does not work even that way.

I got the following answer of the Tempest-EPG developer:

Zitat von K-Vanc @ Github

I never understood properly how that composer thing works. To be honest, I couldn't even manage to install a single file successfully by using composer yet.. so hard to tell you way of fix but at first sight, what I suspect is below 2;

${PUID}=1000=appuser

${PGID}=100=users

docker image set by default to user "nobody" in order to avoid possible clashes with different OS. Also php set into same user so %99, this is your problem. I always see around but dont know the meaning of that 1000/100 numbers. Can you try to install again by changing group and user as nobody ?

Try it now with

PUID=65534

PGID=65534

But if used with Owner / Group "nobody" I assume this will not really fit in the OMV-Standards.

Edit:

Unfortunately no luck; files and folders still not generated below the specified config folder.

Additionally config folder itself seems to be setup with Owner: root, Group: root, Permission: 755 no matter what I have specified through PUID, PGID according to what i see over SSH/SFTP MobaXTerm-SSH-Terminal.

The Solution found on Github with the developer of Tempest-EPG:

It seems that the files and folders of the host (OMV) need to have the same owner and group as inside the container.
Inside the container owner and group is set to "Nobody".

So files and folders at OMV-Level should be set to this Owner / Group as well.

Zitat von K-vanc @ Github

I found below link about problems with mounting folders;

https://forums.docker.com/t/vo…-more-containers/139768/4

It says

Code

You need to make sure the directory/file owner and the processes in all containers that try to access them have the same UID:GID.

I dont know openvault settings but if this true, then folder to be mount and container user/group pids have to be matched(for me this is abit strange need but..). In this case, setting container internal user/group to your system will be very difficult but you can create a new folder and chown it to nobody(you said id is 65534) so UID/GID's of that folder will be same with containers inside. Theoretically, this should work when you mount that folder during container creation

Zitat von K-vanc @ Github

1) stop and hard deleted generated tempest container

2) open your terminal and create a new folder as

Code

sudo mkdir /srv/dev-disk-by-uuid-8b6b6ae4-384d-49c0-9df0-18f8320ada0d/data/system/appdata/tempest_epg/test/

3) set user permissions of that new folder

Code

sudo chown nobody:nogroup /srv/dev-disk-by-uuid-8b6b6ae4-384d-49c0-9df0-18f8320ada0d/data/system/appdata/tempest_epg/test/

Now we created a test folder with same user/group with container to be created

4) edit your composer file as below:

Code

---
version: "2.1"
services:
tempest_epg:
image: kvanc/tempest_epg:latest
container_name: tempest_epg
environment:
- TZ=${TZ}
volumes:
- /srv/dev-disk-by-uuid-8b6b6ae4-384d-49c0-9df0-18f8320ada0d/data/system/appdata/tempest_epg/test/:/var/www/html/tempest_config/
ports:
- 8095:8095
restart: unless-stopped

Alles anzeigen

5) build new container with modified composer file

6) Call tempest.php from your browser and check inside of "/srv/dev-disk-by-uuid-8b6b6ae4-384d-49c0-9df0-18f8320ada0d/data/system/appdata/tempest_epg/test/" to see subfolder generated

Alles anzeigen

Is there any possible way to set the owner and group under which the folders on host will be created directly in the compose-file?

chente:

Actually I`m using SSH/SFTP with MobaXTerm-Terminal. That is not a problem.

The files and folders inside the docker container are set to nobody:nogroup.

The script / container only works correctly if the files and folder on the host system are also set to nobody:nogroup.