How should I give realative path to a docker volume contents?

[janukarhisa]

Ask a Question!

Hello all,

In my docker-compose, there is a volume which is connected to the Airflow DAGs, but Portainer is not taking it correct and which leads to service is falling.

volumes:
- ../../services/airflow/dags/:/opt/airflow/dags/

Project structure:

[Nick-Portainer]

How are you deploying? Via the web editior or via Git? If you are using a Git you can enable reletive paths so you can use relative pathing in your compose file.

If you are using the web editor please use the absolute path name, for example /home/user/services/airflow/dags/ Let me know how you go.

Here is an exmaple of a nginx deployment using the absolute path.

version: '3.3'
services:
  nginx:
    image: nginx:latest
    volumes:
      - /home/pi/testing/html:/usr/share/nginx/html:ro
    ports:
      - "8070:80"
    restart: always

[janukarhisa]

Hey, thanks for the reply. I am using Git, but relative path does not work (../../services/airflow/dags/)

but I managed to do a kind of hack, via container docker volume path /{portainer_docker_volume_path}/compose/{compose number}/services/airflow/dags/ but this gets messy if I delete the stack and redeploy as new.