posts/truenas-docker-pro/

[giscus[bot]]

posts/truenas-docker-pro/

Learn how to run Docker apps on TrueNAS like a pro — with full control, clean YAML, and no extra dashboards.

https://technotim.live/posts/truenas-docker-pro/

[brycemueller]

I don't seem to have the right permissions to edit the ix-apps metadata files on the code server.

[timothystewart6]

Can you post your compose file for code server? It might be how you mapped the volume.

[brycemueller]

services:
code-server:
image: lscr.io/linuxserver/code-server:latest
container_name: code-server
environment:
- PUID=950
- PGID=950
- TZ=America/New_York
volumes:
- ./config:/config
- /mnt/fast/configs/:/apps
- /mnt/.ix-apps/app_configs/:/ix-apps
ports:
- 8443:8443
restart: unless-stopped

[timothystewart6]

I think that folder is owned by root (0) which explains it. I think your choices are modify permissions on that folder to allow 950, which I would be hesitant to do since it's a system folder, or run it as root which is not ideal either but will give you permissions to all of the files and folders you want to manage with code-server. Both are less than ideal but you're using code-server like a file manager so it seems like root might be the easiest route.

[aatsma]

Hi Tim,

Love your content! I ready enjoy your videos.

I have an issue with code-server. I dont see the compose file in code-server. It opens the folder drawio, but do not see the yaml file to edit. Any thoughts?

cheers!

[aatsma]

oops, never mind. Typo in mnt line

[Prkl8r]

I have implemented this and can say it works great! I started by converting some of the TN Apps to custom apps, then using that YAML as the starting point (wow some of those YAMLs were... Interesting).

One question, I can't seem to get .env files working. Have you had luck with this? I'd like to get a system .env with things like common user:group, base IP, common keys, then an app specific .env file. When I tried to get this to work it doesn't look like the docker config is pulling in the values. Not sure if this is a TrueNas limitation or I did something wrong. I reverted back to putting everything in the YAML for now but would like to revert at some point.

[timothystewart6]

As long as you list your .env files it should work.

This is referencing a top level .env

services:
  service1:
    image: something
    env_file:
      - .env

if you have one big stack with multiple services and multiple .env you have to do something like this:

services:
  service1:
    image: something
    env_file:
      - ./service1/.env

  service2:
    image: something
    env_file:
      - ./service2/.env

If you have a top level .env it can only be use for substitution, e.g., and services can only use it if it's passed in

./env

SOME_PATH=/mnt

services:
  service1:
    image: something
    env_file:
      - ./service1/.env
    volumes:
      - ${SOME_PATH}/some/path
      - 
  service2:
    image: something
    env_file:
      - ./service2/.env
    volumes:
      - ${SOME_PATH}/some/path