Incompatibility with Nextcloud Recognize

[eibex]

Hi,

As I have mentioned in the past year in this issue nextcloud/recognize#1096 (please disregard the title, I am using the Debian image, not the Alpine image), there is an issue for which Recognize (a Nextcloud "featured"/"official" app) does not work with the Docker image because it uses Node.js.

Node.js uses the uv_os_homedir function to get the HOME environment variable (for whatever reason) to install ffmpeg (which is otherwise installed just fine with Memories, other apps or simply with apt-get).

This is a "recurring" issue within Docker containers as seen in puppeteer/puppeteer#9230.

I tried setting the HOME variable forcibly when launching docker to a dummy /home/nc-user directory to no avail (even tried creating a user with useradd -m nc-user as suggested in the issue above). Do you have any suggestions in getting this to work and/or potential fixes for all users of this image?

Below the logs for one of the three errors raised (this is the most relevant one):

[recognize] Error: Failed to install ffmpeg: os.js:68
      throw new ERR_SYSTEM_ERROR(ctx);
      ^

SystemError [ERR_SYSTEM_ERROR]: A system error occurred: uv_os_homedir returned ENOENT (no such file or directory)
    at Object.<anonymous> (/var/www/html/custom_apps/recognize/node_modules/env-paths/index.js:5:20)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:93:18)
    at Object.<anonymous> (/var/www/html/custom_apps/recognize/node_modules/ffmpeg-static/install.js:7:18)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) {
  code: 'ERR_SYSTEM_ERROR',
  info: {
    errno: -2,
    code: 'ENOENT',
    message: 'no such file or directory',
    syscall: 'uv_os_homedir'
  },
  errno: [Getter/Setter],
  syscall: [Getter/Setter]
}
	POST /settings/apps/enable
	from xxx

[joshtrichards]

How, precisely, are you running the container? Can you provide a reproducer such as a Compose file that exhibits this behavior?

This might be addressed with #2318, but I don't recall having this problem with recognize off-hand. Though it has been awhile since I used/tested recognize in the Docker admittedly.

Though this is also (arguably) perhaps related to some weird fallback behavior in ffmpeg-static and/or env-paths.

[eibex]

I am running it within Unraid without any fancy compose file.
The command is simply:

docker run
  -d
  --name='Nextcloud'
  --net='bridge'
  --pids-limit 2048
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="redacted"
  -e HOST_CONTAINERNAME="Nextcloud"
  -e 'PHP_MEMORY_LIMIT'='2G'
  -e 'PHP_UPLOAD_LIMIT'='1G'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://xxx.yyy.zzz/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/maschhoff/docker/master/unraid%20xml/nextcloud_logo_square.png'
  -p '2080:80/tcp'
  -v '/mnt/cache/appdata/nextcloud/html':'/var/www/html':'rw'
  -v '/mnt/cache/appdata/nextcloud/apps':'/var/www/html/custom_apps':'rw'
  -v '/mnt/cache/appdata/nextcloud/config':'/var/www/html/config':'rw'
  -v '/mnt/cache/Nextcloud':'/data/nextcloud':'rw'
  --user 99:100
  --log-driver none
  --mount type=tmpfs,destination=/tmp:exec 'nextcloud:31-apache' && docker cp /mnt/cache/scripts/nextcloud_apache.txt Nextcloud:/home/nextcloud_apache.txt && docker exec
  -u root Nextcloud bash
  -c "apt-get update && apt-get install
  -y
  --no-install-recommends nano ffmpeg && a2enmod proxy proxy_http proxy_wstunnel && sed
  -i '28r /home/nextcloud_apache.txt' /etc/apache2/sites-enabled/000-default.conf" && docker restart Nextcloud