Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Batch mode not working, 'plug-in-script-fu-eval' is not available
#1
I had build a local docker environment running GIMP. However when I try to run a gimp batch command I get the following error:
GIMP-Warning: The batch interpreter 'plug-in-script-fu-eval' is not available. Batch mode disabled.

Any idea what might cause this? It works locally but when I deploy it I get this error.
the command I try to run:

gimp --batch-interpreter plug-in-script-fu-eval -i --verbose -d -f -b 'MY COMMAND'

my current dockerfile:
Code:
FROM debian:latest
RUN apt-get update
RUN apt-get install -y gimp --no-install-recommends
RUN apt-get install -y python
RUN rm -rf /var/lib/apt/lists/*
RUN apt-get update
RUN apt-get -qq install curl
RUN apt-get install -y aptitude
RUN curl -sL https://deb.nodesource.com/setup_lts.x | bash - && apt-get install -y nodejs && aptitude install -y npm
RUN apt-get update
# FROM node:lts
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
COPY . .
RUN npm install
RUN apt install -y imagemagick
EXPOSE 8080
CMD ["npm","start"]
Reply
#2
You dockerfile doesn't work for me (and also,why apt-get update twice?).

Code:
Step 14/17 : RUN npm install
---> Running in 4cfce85f19ad
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /usr/src/app/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/usr/src/app/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-12-05T10_14_47_204Z-debug-0.log
The command '/bin/sh -c npm install' returned a non-zero code: 254

Note however that if you don't specify a batch interpreter you get by defaukt the script-fu one:

Code:
root@a610863f4e50:~# gimp  -i --verbose -d -f -b '(gimp-message "Hello from container !!!!!!!!!!!!!!")' -b '(gimp-quit 0)'
Parsing '/etc/gimp/2.0/gimprc' for configured language.
Parsing '/root/.config/GIMP/2.10/gimprc' for configured language.
No language property found.
INIT: gimp_load_config
Parsing '/root/.config/GIMP/2.10/unitrc'
Parsing '/etc/gimp/2.0/gimprc'
Parsing '/root/.config/GIMP/2.10/gimprc'
INIT: gimp_initialize
INIT: gimp_real_initialize
Parsing '/usr/lib/gimp/2.0/interpreters/default.interp'
Parsing '/usr/lib/gimp/2.0/environ/default.env'
INIT: gimp_restore
Parsing '/root/.config/GIMP/2.10/parasiterc'
Parsing '/root/.config/GIMP/2.10/colorrc'
Parsing '/root/.config/GIMP/2.10/templaterc'
INIT: gimp_real_restore
Parsing '/root/.config/GIMP/2.10/pluginrc'
Querying plug-in: '/usr/lib/gimp/2.0/plug-ins/file-rawtherapee/file-rawtherapee'
Querying plug-in: '/usr/lib/gimp/2.0/plug-ins/file-darktable/file-darktable'
Initializing plug-in: '/usr/lib/gimp/2.0/plug-ins/file-rawtherapee/file-rawtherapee'
Initializing plug-in: '/usr/lib/gimp/2.0/plug-ins/file-darktable/file-darktable'
Writing '/root/.config/GIMP/2.10/pluginrc'
Starting extension: 'extension-script-fu'
No batch interpreter specified, using the default 'plug-in-script-fu-eval'.
script-fu-Warning: Hello from container !!!!!!!!!!!!!!

batch command executed successfully
EXIT: gimp_exit
EXIT: gimp_real_exit
Terminating plug-in: '/usr/lib/gimp/2.0/plug-ins/script-fu/script-fu'
Terminating plug-in: '/usr/lib/gimp/2.0/plug-ins/script-fu/script-fu'
Writing '/root/.config/GIMP/2.10/colorrc'
Writing '/root/.config/GIMP/2.10/templaterc'
Writing '/root/.config/GIMP/2.10/parasiterc'
Writing '/root/.config/GIMP/2.10/unitrc'
EXIT: app_exit_after_callback
(running in your semi-broken container)
Reply
#3
(12-05-2022, 10:39 AM)Ofnuts Wrote: You dockerfile doesn't work for me (and also,why apt-get update twice?).

Code:
Step 14/17 : RUN npm install
---> Running in 4cfce85f19ad
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /usr/src/app/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/usr/src/app/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-12-05T10_14_47_204Z-debug-0.log
The command '/bin/sh -c npm install' returned a non-zero code: 254

Note however that if you don't specify a batch interpreter you get by defaukt the script-fu one:

Code:
root@a610863f4e50:~# gimp  -i --verbose -d -f -b '(gimp-message "Hello from container !!!!!!!!!!!!!!")' -b '(gimp-quit 0)'
Parsing '/etc/gimp/2.0/gimprc' for configured language.
Parsing '/root/.config/GIMP/2.10/gimprc' for configured language.
No language property found.
INIT: gimp_load_config
Parsing '/root/.config/GIMP/2.10/unitrc'
Parsing '/etc/gimp/2.0/gimprc'
Parsing '/root/.config/GIMP/2.10/gimprc'
INIT: gimp_initialize
INIT: gimp_real_initialize
Parsing '/usr/lib/gimp/2.0/interpreters/default.interp'
Parsing '/usr/lib/gimp/2.0/environ/default.env'
INIT: gimp_restore
Parsing '/root/.config/GIMP/2.10/parasiterc'
Parsing '/root/.config/GIMP/2.10/colorrc'
Parsing '/root/.config/GIMP/2.10/templaterc'
INIT: gimp_real_restore
Parsing '/root/.config/GIMP/2.10/pluginrc'
Querying plug-in: '/usr/lib/gimp/2.0/plug-ins/file-rawtherapee/file-rawtherapee'
Querying plug-in: '/usr/lib/gimp/2.0/plug-ins/file-darktable/file-darktable'
Initializing plug-in: '/usr/lib/gimp/2.0/plug-ins/file-rawtherapee/file-rawtherapee'
Initializing plug-in: '/usr/lib/gimp/2.0/plug-ins/file-darktable/file-darktable'
Writing '/root/.config/GIMP/2.10/pluginrc'
Starting extension: 'extension-script-fu'
No batch interpreter specified, using the default 'plug-in-script-fu-eval'.
script-fu-Warning: Hello from container !!!!!!!!!!!!!!

batch command executed successfully
EXIT: gimp_exit
EXIT: gimp_real_exit
Terminating plug-in: '/usr/lib/gimp/2.0/plug-ins/script-fu/script-fu'
Terminating plug-in: '/usr/lib/gimp/2.0/plug-ins/script-fu/script-fu'
Writing '/root/.config/GIMP/2.10/colorrc'
Writing '/root/.config/GIMP/2.10/templaterc'
Writing '/root/.config/GIMP/2.10/parasiterc'
Writing '/root/.config/GIMP/2.10/unitrc'
EXIT: app_exit_after_callback
(running in your semi-broken container)

The solution was to change the cloud run container Execution environment from "Default" to "Second Generation", thanks for the help regardless.
Reply


Forum Jump: