Docker compose with Portainer

[BJOHEI]

Been absolutely stumped and I cant figure out how to go about using docker compose to get it running. Got some help from reddit with

services:
  onedrive:
    image: driveone/onedrive:edge
    container_name: onedrive
    environment:
      - ONEDRIVE_UID:1000
      - ONEDRIVE_GID:1000 
      - TZ=Europe/Oslo
    volumes:
      - /srv/dev-disk-by-uuid-10f713a6-3ade-43b8-936d-11820d50eb4f/onedrive/conf:/onedrive/conf #configuration data
      - /srv/dev-disk-by-uuid-10f713a6-3ade-43b8-936d-11820d50eb4f/onedrive/imagebackup/:/onedrive/data #stored data
    restart: unless-stopped

Im running into a auth limbo where I have nowhere to input the auth-link.
Using the above code, can I download the config file into xxxxxx/onedrive/conf and modify it and it will pull what it needs from it, or do I have to put the config file in another path?
The line #stored data, this is where the data is stored I assume, is there a way to tell the compose file that I only want say Pictures/imagebackup in my onedrive to be monitored?

TIA

[abraunegg]

@BJOHEI

Im running into a auth limbo where I have nowhere to input the auth-link

You will need to use /onedrive/conf as the location for any of your auth files as this is what the container has read-write permissions to

Using the above code, can I download the config file into xxxxxx/onedrive/conf and modify it and it will pull what it needs from it, or do I have to put the config file in another path?

Create your 'config' file in this path /srv/dev-disk-by-uuid-10f713a6-3ade-43b8-936d-11820d50eb4f/onedrive/conf so it can be read by the container at startup

The line #stored data, this is where the data is stored I assume, is there a way to tell the compose file that I only want say Pictures/imagebackup in my onedrive to be monitored?

You need to configure the application based on your online data tree. You then use 'sync_list' to reduce the scope of what will be included as changes from the local filesystem and what is synced from online.

If your local directory that you are configuring as the 'sync_dir' is onedrive/imagebackup but this is not your online root .. things will ger messed up very quickly.

My advice is before you start messing around with a container, get the client working outside of a container first with the configuration you are looking for, use --dry-run to ensure validation is done, then replicate that configuration to your container.