Rancher-NFS problem

Archive Rancher 1.x
1

Hi,
there seems to be a problem with rancher-nfs in v 1.6.12

Starting a Service like this fails:

version: '2'
volumes:
  example:
    driver: rancher-nfs
    external: true
services:
  nginx-1:
    image: nginx
    volumes:
    - example:/etc/nginx/conf.d
    - example:/var/www/
    ports:
    - 8081:8081/tcp
    - 8443:8443/tcp

Workaround:
version: ‘2’

services:
  nginx-psxf:
    image: nginx
    volumes:
    - /etc/nginx/conf.d:/etc/nginx/conf.d
    - /var/www/:/var/www/
    ports:
    - 8081:8081/tcp
    - 8443:8443/tcp

The service is created. Next upgrading the Volume via Frontend to the desired configuration works!?

2

You have this in your volume definition:

did you precreate the volume on the storage page? That flag tells rancher to not try to create the volume, that it should already exist. Is that what you are expecting?

3

Hi,
yes I did. Actually, I cloned an other DIR with the “same” service and renamed only the main folder.

Sorry, it might be obvious, but is there a way to get detailed logs of the startup process?

4

It would be nice if Rancher fixed what according to the docker-compose spec is invalid syntax (would save a lot of confusion at the very least) :

external cannot be used in conjunction with other volume configuration keys (driver, driver_opts).