Score:0

PHP-FPM chroot working out of the box, is it normal?

us flag

I'm trying, in a dev box (Ubuntu 20.04), to setup for the first time a chroot.

Here is my PHP-FPM pool (Apache 2.4 as Webserver):

[test]

prefix = /srv/users/$pool

user  = $pool
group = $pool

listen       = /srv/users/$pool/run/php-fpm.sock
listen.owner = $pool
listen.group = www-data
listen.mode  = 660

chroot = $prefix
chdir  = /

env[PATH]   = /usr/local/bin:/usr/bin:/bin
env[TMPDIR] = /srv/users/$pool/tmp
env[TEMP]   = /srv/users/$pool/tmp
env[TMP]    = /srv/users/$pool/tmp

php_admin_value[doc_root]       = /srv/users/$pool/app
php_admin_value[upload_tmp_dir] = /srv/users/$pool/tmp
php_admin_value[sys_temp_dir]   = /srv/users/$pool/tmp

With this setup, without further configurations, I'm able to install Wordpress, use their Plugins store (so, DNS resolution works) send emails with a SMTP configured, etc.

Problem (or not?) is that I've read here, or here that several files need to be either copied over or mount --bind on the chroot to these functions to work.

Who can I make sure my chroot is working properly and not misconfigured?

jp flag
You can always exec `ls /` to verify what is actual root
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.