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

[GH-ISSUE #676] Support ZFS #572

New issue
Closed
opened 2026-02-26 06:33:27 +03:00 by kerem · 7 comments
kerem commented 2026-02-26 06:33:27 +03:00
Owner
Copy link

Originally created by @papatistos on GitHub (Oct 25, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/676

I'm not sure if this should rather be classified as a bug but since zfs is not explicitly supported, I'm putting it as a feature request:

Currently, the container will not work if you map /config onto a zfs volume. The logs will look like this:

[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] 00-app-niceness.sh: executing... ,
[cont-init.d] 00-app-niceness.sh: exited 0.,
[cont-init.d] 00-app-script.sh: executing... ,
[cont-init.d] 00-app-script.sh: exited 0.,
[cont-init.d] 00-app-user-map.sh: executing... ,
[cont-init.d] 00-app-user-map.sh: exited 0.,
[cont-init.d] 00-clean-logmonitor-states.sh: executing... ,
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.,
[cont-init.d] 00-clean-tmp-dir.sh: executing... ,
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.,
[cont-init.d] 00-set-app-deps.sh: executing... ,
[cont-init.d] 00-set-app-deps.sh: exited 0.,
[cont-init.d] 00-set-home.sh: executing... ,
[cont-init.d] 00-set-home.sh: exited 0.,
[cont-init.d] 00-take-config-ownership.sh: executing... ,
[cont-init.d] 00-take-config-ownership.sh: exited 0.,
[cont-init.d] 00-xdg-runtime-dir.sh: executing... ,
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.,
[cont-init.d] nginx-proxy-manager.sh: executing... ,
[cont-init.d] nginx-proxy-manager.sh: Initializing database data directory...,
[cont-init.d] nginx-proxy-manager.sh: exited 1.,
[services.d] stopping services,
[services.d] stopping s6-fdholderd...,
[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] syncing disks.,
[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] 00-app-niceness.sh: executing... ,
[cont-init.d] 00-app-niceness.sh: exited 0.,
[cont-init.d] 00-app-script.sh: executing... ,
[cont-init.d] 00-app-script.sh: exited 0.,
[cont-init.d] 00-app-user-map.sh: executing... ,
[cont-init.d] 00-app-user-map.sh: exited 0.,
[cont-init.d] 00-clean-logmonitor-states.sh: executing... ,
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.,
[cont-init.d] 00-clean-tmp-dir.sh: executing... ,
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.,
[cont-init.d] 00-set-app-deps.sh: executing... ,
[cont-init.d] 00-set-app-deps.sh: exited 0.,
[cont-init.d] 00-set-home.sh: executing... ,
[cont-init.d] 00-set-home.sh: exited 0.,
[cont-init.d] 00-take-config-ownership.sh: executing... ,
[cont-init.d] 00-take-config-ownership.sh: exited 0.,
[cont-init.d] 00-xdg-runtime-dir.sh: executing... ,
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.,
[cont-init.d] nginx-proxy-manager.sh: executing... ,
[cont-init.d] nginx-proxy-manager.sh: Initializing database data directory...,
[cont-init.d] nginx-proxy-manager.sh: exited 1.,
[services.d] stopping services,
[services.d] stopping s6-fdholderd...,
[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] syncing disks.,
[s6-finish] sending all processes the TERM signal.,

It took me a felt eternity to figure out that the reason why this wasn't working was that I was using the "wrong" filesystem. zfs doesn't work because apparently it doesn't support fallocate (which NPM seems to use).

So if it is possible to avoid fallocate, that would make NPM compatible with zfs. I can see, though, that this is probably not a priority for you so I'd like to suggest to warn users about this (either in the instructions) or, ideally, by detecting that fallocate is not working and issuing and error about this (and possibly stopping the container).

Originally created by @papatistos on GitHub (Oct 25, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/676 I'm not sure if this should rather be classified as a bug but since zfs is not explicitly supported, I'm putting it as a feature request: Currently, the container will not work if you map `/config` onto a zfs volume. The logs will look like this: ~~~~ [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] 00-app-niceness.sh: executing... , [cont-init.d] 00-app-niceness.sh: exited 0., [cont-init.d] 00-app-script.sh: executing... , [cont-init.d] 00-app-script.sh: exited 0., [cont-init.d] 00-app-user-map.sh: executing... , [cont-init.d] 00-app-user-map.sh: exited 0., [cont-init.d] 00-clean-logmonitor-states.sh: executing... , [cont-init.d] 00-clean-logmonitor-states.sh: exited 0., [cont-init.d] 00-clean-tmp-dir.sh: executing... , [cont-init.d] 00-clean-tmp-dir.sh: exited 0., [cont-init.d] 00-set-app-deps.sh: executing... , [cont-init.d] 00-set-app-deps.sh: exited 0., [cont-init.d] 00-set-home.sh: executing... , [cont-init.d] 00-set-home.sh: exited 0., [cont-init.d] 00-take-config-ownership.sh: executing... , [cont-init.d] 00-take-config-ownership.sh: exited 0., [cont-init.d] 00-xdg-runtime-dir.sh: executing... , [cont-init.d] 00-xdg-runtime-dir.sh: exited 0., [cont-init.d] nginx-proxy-manager.sh: executing... , [cont-init.d] nginx-proxy-manager.sh: Initializing database data directory..., [cont-init.d] nginx-proxy-manager.sh: exited 1., [services.d] stopping services, [services.d] stopping s6-fdholderd..., [cont-finish.d] executing container finish scripts..., [cont-finish.d] done., [s6-finish] syncing disks., [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] 00-app-niceness.sh: executing... , [cont-init.d] 00-app-niceness.sh: exited 0., [cont-init.d] 00-app-script.sh: executing... , [cont-init.d] 00-app-script.sh: exited 0., [cont-init.d] 00-app-user-map.sh: executing... , [cont-init.d] 00-app-user-map.sh: exited 0., [cont-init.d] 00-clean-logmonitor-states.sh: executing... , [cont-init.d] 00-clean-logmonitor-states.sh: exited 0., [cont-init.d] 00-clean-tmp-dir.sh: executing... , [cont-init.d] 00-clean-tmp-dir.sh: exited 0., [cont-init.d] 00-set-app-deps.sh: executing... , [cont-init.d] 00-set-app-deps.sh: exited 0., [cont-init.d] 00-set-home.sh: executing... , [cont-init.d] 00-set-home.sh: exited 0., [cont-init.d] 00-take-config-ownership.sh: executing... , [cont-init.d] 00-take-config-ownership.sh: exited 0., [cont-init.d] 00-xdg-runtime-dir.sh: executing... , [cont-init.d] 00-xdg-runtime-dir.sh: exited 0., [cont-init.d] nginx-proxy-manager.sh: executing... , [cont-init.d] nginx-proxy-manager.sh: Initializing database data directory..., [cont-init.d] nginx-proxy-manager.sh: exited 1., [services.d] stopping services, [services.d] stopping s6-fdholderd..., [cont-finish.d] executing container finish scripts..., [cont-finish.d] done., [s6-finish] syncing disks., [s6-finish] sending all processes the TERM signal., ~~~~ It took me a felt eternity to figure out that the reason why this wasn't working was that I was using the "wrong" filesystem. zfs doesn't work because apparently it doesn't support `fallocate` (which NPM seems to use). So if it is possible to avoid `fallocate`, that would make NPM compatible with zfs. I can see, though, that this is probably not a priority for you so I'd like to suggest to warn users about this (either in the instructions) or, ideally, by detecting that `fallocate` is not working and issuing and error about this (and possibly stopping the container).
kerem 2026-02-26 06:33:27 +03:00
kerem commented 2026-02-26 06:33:28 +03:00
Author
Owner
Copy link

@Wadera commented on GitHub (Oct 27, 2020):

Are you sure that you configured docker correctly? Mine works as expected.

Check this:

root@myhost:~# docker info | grep zfs
 Storage Driver: zfs

https://docs.docker.com/storage/storagedriver/zfs-driver/

<!-- gh-comment-id:717469150 --> @Wadera commented on GitHub (Oct 27, 2020): Are you sure that you configured docker correctly? Mine works as expected. Check this: ``` root@myhost:~# docker info | grep zfs Storage Driver: zfs ``` https://docs.docker.com/storage/storagedriver/zfs-driver/
kerem commented 2026-02-26 06:33:28 +03:00
Author
Owner
Copy link

@papatistos commented on GitHub (Oct 29, 2020):

Maybe there is a missunderstanding: by "zfs volume", I didn't mean a docker volume (strictly speaking) but a binding to a zfs directory on the host). Like this:

image

If I missunderstood, could you explain some more? docker info | grep zfs returns nothing. So does docker info | grep storage

<!-- gh-comment-id:718280834 --> @papatistos commented on GitHub (Oct 29, 2020): Maybe there is a missunderstanding: by "zfs volume", I didn't mean a docker volume (strictly speaking) but a binding to a zfs directory on the host). Like this: ![image](https://user-images.githubusercontent.com/3662750/97510097-43467300-1984-11eb-91c9-5989f0e817ec.png) If I missunderstood, could you explain some more? `docker info | grep zfs` returns nothing. So does `docker info | grep storage`
kerem commented 2026-02-26 06:33:28 +03:00
Author
Owner
Copy link

@Wadera commented on GitHub (Oct 31, 2020):

If it doesn't show nothing - that's mean you didn't have configured ZFS storage driver.
It's not NPM issue, but docker configuration.
More about Docker ZFS support here: https://docs.docker.com/storage/storagedriver/zfs-driver/

<!-- gh-comment-id:719950922 --> @Wadera commented on GitHub (Oct 31, 2020): If it doesn't show nothing - that's mean you didn't have configured ZFS storage driver. It's not NPM issue, but docker configuration. More about Docker ZFS support here: https://docs.docker.com/storage/storagedriver/zfs-driver/
kerem commented 2026-02-26 06:33:28 +03:00
Author
Owner
Copy link

@papatistos commented on GitHub (May 15, 2021):

If it doesn't show nothing - that's mean you didn't have configured ZFS storage driver.

I'm not sure why I would need the ZFS storage driver. I'm running about 15 docker containers, all of which use the zfs storage without any issues.

You never said anything about this:

zfs doesn't work because apparently it doesn't support fallocate (which NPM seems to use).

So if it is possible to avoid fallocate, that would make NPM compatible with zfs.

Is it not possible to avoid fallocate?

<!-- gh-comment-id:841734370 --> @papatistos commented on GitHub (May 15, 2021): > If it doesn't show nothing - that's mean you didn't have configured ZFS storage driver. I'm not sure why I would need the ZFS storage driver. I'm running about 15 docker containers, all of which use the zfs storage without any issues. You never said anything about this: >zfs doesn't work because apparently it doesn't support fallocate (which NPM seems to use). > >So if it is possible to avoid fallocate, that would make NPM compatible with zfs. Is it not possible to avoid `fallocate`?
kerem commented 2026-02-26 06:33:28 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (May 16, 2021):

At least the sqlite3 npm package seems to use fallocate, which is a database option via knex.
If anyone wants to try and prevent usage of this when sqlite is not used to see if it helps, PRs are welcome.

<!-- gh-comment-id:841790510 --> @chaptergy commented on GitHub (May 16, 2021): At least the sqlite3 npm package seems to use `fallocate`, which is a database option via knex. If anyone wants to try and prevent usage of this when sqlite is not used to see if it helps, PRs are welcome.
kerem commented 2026-02-26 06:33:28 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Mar 24, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2016661945 --> @github-actions[bot] commented on GitHub (Mar 24, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 06:33:28 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (May 4, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2848914102 --> @github-actions[bot] commented on GitHub (May 4, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/prod-minor-updates-5edfafad3a
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/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#572
No description provided.