starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #784] DB wont start with Volume on NFS Mount #662

New issue
Closed
opened 2026-02-26 06:33:53 +03:00 by kerem · 1 comment
kerem commented 2026-02-26 06:33:53 +03:00
Owner
Copy link

Originally created by @Blackraz0r on GitHub (Dec 19, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/784

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image
  • yes -> yes
  • Are you sure you're not using someone else's docker image?
  • yes
  • If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
  • irrelevant

latest docker images ( i created the compose file like on the website described)
2.7.1
Compose file:

version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: always
    ports:
      # Public HTTP Port:
      - '80:80'
      # Public HTTPS Port:
      - '443:443'
      # Admin Web Port:
      - '81:81'
    environment:
      # These are the settings to access your db
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "npm"
      DB_MYSQL_NAME: "npm"
      # If you would rather use Sqlite uncomment this
      # and remove all DB_MYSQL_* lines above
      # DB_SQLITE_FILE: "/data/database.sqlite"
      # Uncomment this if IPv6 is not enabled on your host
      DISABLE_IPV6: 'true'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    depends_on:
      - db
  db:
    image: jc21/mariadb-aria:10.4
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: 'npm'
    volumes:
      - ./db:/var/lib/mysql

i run my docker host via ubuntu 16.04 and my NAS (NFS-MOUNT) is a synology one.
this is the nfs configuration on the nas:
https://i.imgur.com/74YYup5.png
the ip is the ip of the docker host.
so from the side of the nas nfs works ( other containers work too)

Describe the bug
when i login it shows "Bad Gateway"
https://i.imgur.com/Bt1w8EO.png

To Reproduce

  1. create a new folder on the nas:
    sudo mkdir /mnt/NAS/docker/volumes/NPM

  2. create compose file
    sudo nano docker-compose.yml
    paste the contents from above

  3. run the stack
    sudo docker-compose up -d

  4. Log into NPM via hostIP:81

  5. get bad gateweay like in the screen above

Expected behavior
i can normally login

Screenshots
see above situational
Operating System
Ubuntu16.04 / Docker 19.03.12 / docker-compose version 1.25.5, build 8a1c60f6
Additional context

here comes the fun part.
the database seems to use a user that does no have permission of the nfs mount.
https://i.imgur.com/fqVOGuv.png
in this case the user is "systemd-network"
so how can i force the database to use root ?

because this seems to be problematic when the db want to start somehow:

MySQL init process done. Ready for start up.
exec /usr/bin/mysqld --user=mysql --console --skip-name-resolve --skip-networking=0
2020-12-19 22:02:18 0 [Note] /usr/bin/mysqld (mysqld 10.4.12-MariaDB) starting as process 1 ...
2020-12-19 22:02:18 0 [Note] InnoDB: Using Linux native AIO
2020-12-19 22:02:18 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-12-19 22:02:18 0 [Note] InnoDB: Uses event mutexes
2020-12-19 22:02:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-12-19 22:02:18 0 [Note] InnoDB: Number of pools: 1
2020-12-19 22:02:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-12-19 22:02:18 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2020-12-19 22:02:18 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-12-19 22:02:18 0 [Note] InnoDB: Completed initialization of buffer pool
2020-12-19 22:02:18 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-12-19 22:02:18 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2020-12-19 22:02:18 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-12-19 22:02:19 0 [Note] InnoDB: Starting shutdown...
2020-12-19 22:02:19 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-12-19 22:02:19 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-12-19 22:02:19 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-12-19 22:02:19 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2020-12-19 22:02:19 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-12-19 22:02:19 0 [ERROR] Aborting
[i] mysqld already present, skipping creation
[i] MySQL data directory not found, creating initial DBs
2020-12-19 22:02:46 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2020-12-19 22:02:46 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-12-19 22:02:47 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-12-19 22:02:47 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-12-19 22:02:47 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-12-19 22:02:47 0 [ERROR] Aborting
 Creating database: npm
[i] with character set: 'utf8' and collation: 'utf8_general_ci'
[i] Creating user: npm with password npm
2020-12-19 22:02:47 0 [Note] /usr/bin/mysqld (mysqld 10.4.12-MariaDB) starting as process 54 ...
2020-12-19 22:02:47 0 [Note] InnoDB: Using Linux native AIO
2020-12-19 22:02:47 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-12-19 22:02:47 0 [Note] InnoDB: Uses event mutexes
2020-12-19 22:02:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-12-19 22:02:47 0 [Note] InnoDB: Number of pools: 1
2020-12-19 22:02:47 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-12-19 22:02:47 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2020-12-19 22:02:47 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-12-19 22:02:47 0 [Note] InnoDB: Completed initialization of buffer pool
2020-12-19 22:02:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-12-19 22:02:47 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2020-12-19 22:02:47 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-12-19 22:02:48 0 [Note] InnoDB: Starting shutdown...
2020-12-19 22:02:48 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-12-19 22:02:48 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-12-19 22:02:48 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-12-19 22:02:48 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-12-19 22:02:48 0 [ERROR] Aborting
/scripts/run.sh: ignoring or entrypoint initdb empty /docker-entrypoint-initdb.d/*
MySQL init process done. Ready for start up.

this is a repeating pattern

and the npm container is like this:

[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/production.conf
  ❯ /etc/nginx/conf.d/default.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/proxy.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /data/nginx
[12/19/2020] [10:03:44 PM] [Global   ] › ✖  error     connect ECONNREFUSED 192.168.48.3:3306
[12/19/2020] [10:03:45 PM] [Global   ] › ✖  error     connect ECONNREFUSED 192.168.48.3:3306
[12/19/2020] [10:03:46 PM] [Global   ] › ✖  error     connect ECONNREFUSED 192.168.48.3:3306
[12/19/2020] [10:03:47 PM] [Global   ] › ✖  error     connect ECONNREFUSED 192.168.48.3:3306
[12/19/2020] [10:03:48 PM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND db
[12/19/2020] [10:03:49 PM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND db
[12/19/2020] [10:03:50 PM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND db
[12/19/2020] [10:03:51 PM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND db
[12/19/2020] [10:03:52 PM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND db
[12/19/2020] [10:03:53 PM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND db

it waits on the db i guess?

anyway to fix that issue with nfs mounts ?
i reall dont want to story my file nonredudnant on a vm. i mean it violates thhe whole purpose of a nas

thank you in advance guys!

Originally created by @Blackraz0r on GitHub (Dec 19, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/784 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image - yes -> yes - Are you sure you're not using someone else's docker image? - yes - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? - irrelevant latest docker images ( i created the compose file like on the website described) 2.7.1 Compose file: ``` version: "3" services: app: image: 'jc21/nginx-proxy-manager:latest' restart: always ports: # Public HTTP Port: - '80:80' # Public HTTPS Port: - '443:443' # Admin Web Port: - '81:81' environment: # These are the settings to access your db DB_MYSQL_HOST: "db" DB_MYSQL_PORT: 3306 DB_MYSQL_USER: "npm" DB_MYSQL_PASSWORD: "npm" DB_MYSQL_NAME: "npm" # If you would rather use Sqlite uncomment this # and remove all DB_MYSQL_* lines above # DB_SQLITE_FILE: "/data/database.sqlite" # Uncomment this if IPv6 is not enabled on your host DISABLE_IPV6: 'true' volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt depends_on: - db db: image: jc21/mariadb-aria:10.4 restart: always environment: MYSQL_ROOT_PASSWORD: 'npm' MYSQL_DATABASE: 'npm' MYSQL_USER: 'npm' MYSQL_PASSWORD: 'npm' volumes: - ./db:/var/lib/mysql ``` i run my docker host via ubuntu 16.04 and my NAS (NFS-MOUNT) is a synology one. this is the nfs configuration on the nas: https://i.imgur.com/74YYup5.png the ip is the ip of the docker host. so from the side of the nas nfs works ( other containers work too) **Describe the bug** when i login it shows "Bad Gateway" https://i.imgur.com/Bt1w8EO.png **To Reproduce** 1. create a new folder on the nas: `sudo mkdir /mnt/NAS/docker/volumes/NPM` 2. create compose file `sudo nano docker-compose.yml` paste the contents from above 3. run the stack `sudo docker-compose up -d` 4. Log into NPM via hostIP:81 5. get bad gateweay like in the screen above **Expected behavior** i can normally login **Screenshots** see above situational **Operating System** Ubuntu16.04 / Docker 19.03.12 / docker-compose version 1.25.5, build 8a1c60f6 **Additional context** here comes the fun part. the database seems to use a user that does no have permission of the nfs mount. https://i.imgur.com/fqVOGuv.png in this case the user is "systemd-network" so how can i force the database to use root ? because this seems to be problematic when the db want to start somehow: ``` MySQL init process done. Ready for start up. exec /usr/bin/mysqld --user=mysql --console --skip-name-resolve --skip-networking=0 2020-12-19 22:02:18 0 [Note] /usr/bin/mysqld (mysqld 10.4.12-MariaDB) starting as process 1 ... 2020-12-19 22:02:18 0 [Note] InnoDB: Using Linux native AIO 2020-12-19 22:02:18 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-12-19 22:02:18 0 [Note] InnoDB: Uses event mutexes 2020-12-19 22:02:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-12-19 22:02:18 0 [Note] InnoDB: Number of pools: 1 2020-12-19 22:02:18 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-12-19 22:02:18 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts) 2020-12-19 22:02:18 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2020-12-19 22:02:18 0 [Note] InnoDB: Completed initialization of buffer pool 2020-12-19 22:02:18 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-12-19 22:02:18 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages! 2020-12-19 22:02:18 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2020-12-19 22:02:19 0 [Note] InnoDB: Starting shutdown... 2020-12-19 22:02:19 0 [ERROR] Plugin 'InnoDB' init function returned error. 2020-12-19 22:02:19 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2020-12-19 22:02:19 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-12-19 22:02:19 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded 2020-12-19 22:02:19 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2020-12-19 22:02:19 0 [ERROR] Aborting [i] mysqld already present, skipping creation [i] MySQL data directory not found, creating initial DBs 2020-12-19 22:02:46 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages! 2020-12-19 22:02:46 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2020-12-19 22:02:47 0 [ERROR] Plugin 'InnoDB' init function returned error. 2020-12-19 22:02:47 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2020-12-19 22:02:47 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2020-12-19 22:02:47 0 [ERROR] Aborting Creating database: npm [i] with character set: 'utf8' and collation: 'utf8_general_ci' [i] Creating user: npm with password npm 2020-12-19 22:02:47 0 [Note] /usr/bin/mysqld (mysqld 10.4.12-MariaDB) starting as process 54 ... 2020-12-19 22:02:47 0 [Note] InnoDB: Using Linux native AIO 2020-12-19 22:02:47 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-12-19 22:02:47 0 [Note] InnoDB: Uses event mutexes 2020-12-19 22:02:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-12-19 22:02:47 0 [Note] InnoDB: Number of pools: 1 2020-12-19 22:02:47 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-12-19 22:02:47 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts) 2020-12-19 22:02:47 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2020-12-19 22:02:47 0 [Note] InnoDB: Completed initialization of buffer pool 2020-12-19 22:02:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-12-19 22:02:47 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages! 2020-12-19 22:02:47 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2020-12-19 22:02:48 0 [Note] InnoDB: Starting shutdown... 2020-12-19 22:02:48 0 [ERROR] Plugin 'InnoDB' init function returned error. 2020-12-19 22:02:48 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2020-12-19 22:02:48 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-12-19 22:02:48 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2020-12-19 22:02:48 0 [ERROR] Aborting /scripts/run.sh: ignoring or entrypoint initdb empty /docker-entrypoint-initdb.d/* MySQL init process done. Ready for start up. ``` this is a repeating pattern and the npm container is like this: ``` [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. Disabling IPV6 in hosts ❯ Disabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/production.conf ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/resolvers.conf Disabling IPV6 in hosts ❯ Disabling IPV6 in hosts: /data/nginx [12/19/2020] [10:03:44 PM] [Global ] › ✖ error connect ECONNREFUSED 192.168.48.3:3306 [12/19/2020] [10:03:45 PM] [Global ] › ✖ error connect ECONNREFUSED 192.168.48.3:3306 [12/19/2020] [10:03:46 PM] [Global ] › ✖ error connect ECONNREFUSED 192.168.48.3:3306 [12/19/2020] [10:03:47 PM] [Global ] › ✖ error connect ECONNREFUSED 192.168.48.3:3306 [12/19/2020] [10:03:48 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db [12/19/2020] [10:03:49 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db [12/19/2020] [10:03:50 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db [12/19/2020] [10:03:51 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db [12/19/2020] [10:03:52 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db [12/19/2020] [10:03:53 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db ``` it waits on the db i guess? anyway to fix that issue with nfs mounts ? i reall dont want to story my file nonredudnant on a vm. i mean it violates thhe whole purpose of a nas thank you in advance guys!
kerem 2026-02-26 06:33:53 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 06:33:53 +03:00
Author
Owner
Copy link

@ahgraber commented on GitHub (Feb 8, 2021):

Using recent versions (>=3.2, I think?) of docker-compose, you can create docker volumes that point to the NFS share and use them as the mountpoints under services. You don't even have to mount the nfs volume on the docker host -- docker will manage it all!

limited compose example:

version 3.7

services:
  app:
    ...
  mariadb:
    ...
    volumes:
      - db-mount:/var/lib/mysql  # db-mount is the name of the nfs mount volume this replaces the local mount

volumes:
  db-mount:
    driver: local
    driver_opts:
      type: nfs
      o: nfsvers=4,addr=<YOUR NAS IP>,rw,retry=1,soft,nolock
      device: ":/db"

in o: you're providing mount options:
rw for read/write,
soft allows I/O interruptions (i.e., doesn't crash your container if there's a network blip)
nolock allows multiple readers
in device: you're providing the specific path to the share on your nas. Might be ":/db" or might be ":/path/to/share"

Ref: https://stackoverflow.com/questions/45282608/how-to-directly-mount-nfs-share-volume-in-container-using-docker-compose-v3

<!-- gh-comment-id:775185965 --> @ahgraber commented on GitHub (Feb 8, 2021): Using recent versions (>=3.2, I think?) of docker-compose, you can create docker volumes that point to the NFS share and use them as the mountpoints under services. You don't even have to mount the nfs volume on the docker host -- docker will manage it all! limited compose example: ```yml version 3.7 services: app: ... mariadb: ... volumes: - db-mount:/var/lib/mysql # db-mount is the name of the nfs mount volume this replaces the local mount volumes: db-mount: driver: local driver_opts: type: nfs o: nfsvers=4,addr=<YOUR NAS IP>,rw,retry=1,soft,nolock device: ":/db" ``` in `o:` you're providing mount options: rw for read/write, soft allows I/O interruptions (i.e., doesn't crash your container if there's a network blip) nolock allows multiple readers in `device:` you're providing the specific path to the share on your nas. Might be ":/db" or might be ":/path/to/share" Ref: https://stackoverflow.com/questions/45282608/how-to-directly-mount-nfs-share-volume-in-container-using-docker-compose-v3
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#662
No description provided.