¿Es posible ejecutar Google-chrome no Chromium con titiritero en AWS Lambda con contenedor?

Script atascado cuando creo una nueva página en el navegador:

 const page = await browser.newPage();

Registros de AWS lambda:

 mkdir: cannot create directory '/.local': Read-only file system touch: cannot touch '/.local/share/applications/mimeapps.list': No such file or directory /usr/bin/google-chrome-stable: line 45: /dev/fd/62: No such file or directory /usr/bin/google-chrome-stable: line 46: /dev/fd/62: No such file or directory [0213/000419.523205:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [0213/000419.528197:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [0213/000419.648505:WARNING:audio_manager_linux.cc(60)] Falling back to ALSA for audio output. PulseAudio is not available or could not be initialized. DevTools listening on ws://127.0.0.1:46195/devtools/browser/1d348770-1c99-48a5-934c-fae5254fc766 [0213/000419.769218:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable. prctl(PR_SET_NO_NEW_PRIVS) failed prctl(PR_SET_NO_NEW_PRIVS) failed