#Cant set up config.yml

1 messages · Page 1 of 1 (latest)

twilit knoll
#

I am on a docker image kometa/kometa, on ubuntu. No matter what I do I have not been able to have the container rid of this message even though I have modified it:
"Configuration File ('config.yml') has been downloaded from GitHub (Branch: 'master') and saved as '//config/config.yml'. Please update this file with your API keys and other required settings."

I have added in all my information within the config file it generated and it doesn't not have a .template extension, simply "config.yml". There are no other logs showing.

half hemlockBOT
#

Welcome @twilit knoll!

Someone from <@&938443185347244033> will assist when they're available.

Including meta.log from the beginning is a huge help. Type !logs for more information.

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

#

You can press the "Close Post" button above or type /close at any time to close this post.

wintry sparrow
#

are you running via docker compose?

#

or how is your mapping of your Kometa instance?

fierce whale
#

This is what happens if Kometa cannot see /config/config.yml from inside the container. Almost certainly this is a volume mapping or file name issue.

wintry sparrow
#

mapping can be confusing when setting up... /config/config.yml does not mean /path/to/kometa/config:/config. But does mean that whatever is on the right side (container path) cannot find that config file.

So the config file needs to be be placed exactly in whatever path you have on the left side (host path).
your host path could be:
/path/to/kometa/config or it could be
/path/to/kometa or
/some/other/path. but the file must be located in your host path

twilit knoll
#

Let me get some information together for you guys... Yes I am using docker compose.

wintry sparrow
flat trenchBOT
#
Using Code Blocks

Please use code blocks when sending any code-related text (such as error messages or configuration file extracts.)

The Grave Accent key (`) is used to define code blocks and is typically found to the left of the number 1 key on a standard keyboard.

If you are posting any yaml-formatted text (such as collections), you can add yaml to your Grave Accent keys for coloured formatting. See the below sample text and output

YOU TYPE THIS

`​`​`yaml
collections:
  Documentaries:
    smart_filter:
      all:
        genre: Documentary
`​`​`

DISCORD DISPLAYS

collections:
  Documentaries:
    smart_filter:
      all:
        genre: Documentary
twilit knoll
#

anchors used in the compose

x-common-keys-media: &common-keys-media
  networks:
    - npm_proxy
  security_opt:
    - no-new-privileges:true
  restart: "no"
x-environment: &default-tz-puid-pgid
  TZ: $TZ
  PUID: $PUID
  PGID: $PGID

Kometa

kometa:
    <<: *common-keys-media
    image: kometateam/kometa:latest
    container_name: kometa
    networks:
      npm_proxy:
        ipv4_address: 10.0.0.176
    volumes:
      - $DOCKERDIR/appdata/Kometa:/config:rw
    environment:
      <<: *default-tz-puid-pgid```


From fresh, the image downloads the config.yml to here:

``` ~/Docker/appdata/Kometa```
See image for attached volume
#

wow hold on sorry

wintry sparrow
#

so what is the full path of where you have your config installed?

twilit knoll
#

/home/cavnfox/Docker/appdata/Kometa

#

just doubled checked

wintry sparrow
#

what does $DOCKERDIR refer to; that's important that it's correct

twilit knoll
wintry sparrow
#

so in /home/cavnfox/Docker/appdata/Kometa what do you get when you type ls -la

twilit knoll
#

mind the server name, my girlfriend wanted to name it haha

wintry sparrow
#

and is that config.yml yours?

#

and what's in the environment variables

twilit knoll
wintry sparrow
#

my config has different permissions

twilit knoll
#

what are they?

wintry sparrow
#

don't know if that matters, but that's what mine have always been

fierce whale
#

Given that the logs dir and UUID file are owned by root, the container appears to be running as root. I wouldn't expect that root would be unable to read a file created by another user, put perhaps?

wintry sparrow
#

you would think, but not sure why Kometa doesn't see the config file

fierce whale
#

So when you run Kometa you get a config.yml.template right next to those files in that directory?

#

Who owns it? What happens if you make your config.yml match that?

twilit knoll
#

Thats the thing, this is the config file that downloads

#

there is no .template

fierce whale
#

Oh, that's right.

#

When it downloads, is it owned by root?

twilit knoll
#

Yes it is owned by root when it downloads

#

and i saw before it was owned by my user. so i retested it with the ownership of root of config.yml and still same issue

fierce whale
#

Hm, so not that.

#

The next thing I'd try would be starting the container with an ls -al /config instead of letting the script run. Can't remember what you have to override for that.

twilit knoll
#

I just verified the file path within the container console.

First, sanity check, same user and group within the container can read and write config.yml. And I threw in a random "IAMHERE.txt" from within the container console to verifiy its location on my server, and it indeed ended up at ~/Docker/appdata/Kometa

#
total 32
drwxr-xr-x+ 3 root root 4096 Oct 25 19:51 .
drwxr-xr-x  1 root root 4096 Oct 25 19:49 ..
-rw-rw-r--+ 1 root root    0 Oct 25 19:49 IAMHERE.txt
-rw-rw-r--+ 1 root root   36 Oct 25 16:27 UUID
-rw-rw-r--+ 1 root root 6437 Oct 25 19:51 config.yml
drwxrwxr-x+ 2 root root 4096 Oct 25 16:27 logs
root@da581b21faf6:/config# whoami
root```
#

So it is mapping correctly...

wintry sparrow
#

You’re setting puid and pgid, so shouldn’t the container be running as that user and not root? Probably has nothing to do with it, but seems weird.

twilit knoll
#

i am newer to permissions in linux but i assumed that from the containers POV it is root to what it accesses

twilit knoll
wintry sparrow
#

What happens if you add an environment variable
user: 1000:1000

honestly just trying to figure out what might work

fierce whale
#

The Kometa image doesn't support PGID/PUID. You can use user in docker compose

twilit knoll
#

that did something:

No log line matching the '' filter```
fierce whale
#

Probably waiting to run now.

twilit knoll
#

what is the best way to verify it is working?

fierce whale
#

If the container is up, it's waiting until 5am to run.

#

The two options are run and exit immediately, or sit and wait to wake up.

twilit knoll
#

alright, ill ensure my config is set up to how i want and I will let you guys know tomorrow if something pops up!

wintry sparrow
#

You can add a variable in the compose file for run now. And then it would run now and exit. Or you can just wait till it’s run time

twilit knoll
#

Looks good, now I will just learn how to set this up... Thanks!