getting an error when deploying mern website to railway - node.js

i have a discord clone portfolio project at https://github.com/Inferno-Ripper/discord-clone
i have deployed the frontend to vercel https://inferno-ripper-discord-clone.vercel.app, it works fine on firefox but it doesn't work on chrome and edge the network requests are stuck on pending.
i have the backend hosted on railway, but when i try to deploy the frontend to railway it doesn't work i get this error
Build Logs on Railway
==============
Using Nixpacks
==============
Inline cache enabled
no image tag to read cache from
╔═════════ Nixpacks v1.0.0 ═════════╗
║ setup │ nodejs-16_x, npm-8_x ║
║───────────────────────────────────║
║ install │ npm ci ║
║───────────────────────────────────║
║ build │ npm run build ║
║───────────────────────────────────║
║ start │ npm run start ║
╚═══════════════════════════════════╝
#1 [internal] load build definition from Dockerfile
#1 sha256:8877270a0c7cc13a2a9d5d8d7622cdc0ed73b70ab957d081f5d2851376bd3d8b
#1 transferring dockerfile: 2.08kB done
#1 DONE 0.1s
#2 [internal] load .dockerignore
#2 sha256:2affaad88737ba21b452b724bb2eb7f99ebe9375f3ecc65cb617a265f26c24d8
#2 transferring context:
#2 transferring context: 2B done
#2 DONE 0.2s
#3 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1671044363
#3 sha256:d2df4677b7c4c8365aa628f14d4cbdd9867466b6b454c21060180de4b7936a2e
#3 DONE 0.2s
#4 [stage-0 1/10] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1671044363#sha256:4df36f942799b8b727c8648ca4fa05d9cd2526e41e7994665082c0f7ef03d95b
#4 sha256:a20b8f1ac783d9d00f7c673a9ef0cf3b8f0aaee89856a86f7aff78cda1934897
#4 DONE 0.0s
#5 [stage-0 2/10] WORKDIR /app/
#5 sha256:46f35bb14209f31cddb6d0e80d42b3ceb58d2f45672a3486e22a069140ac06a3
#5 CACHED
#6 [internal] load build context
#6 sha256:5648a1c35d09c4517e30329702fb9cb16d3deaa95854bbf8005030d88d65df40
#6 transferring context: 1.35MB 0.0s done
#6 DONE 0.1s
#7 [stage-0 3/10] COPY .nixpacks/nixpkgs-ffca9ffaaafb38c8979068cee98b2644bd3f14cb.nix .nixpacks/nixpkgs-ffca9ffaaafb38c8979068cee98b2644bd3f14cb.nix
#7 sha256:27a0f7b0a4acef0e435ab6d4d2af6e3163455490546099ce36a6ce8090fa6663
#7 CACHED
#8 [stage-0 4/10] RUN nix-env -if .nixpacks/nixpkgs-ffca9ffaaafb38c8979068cee98b2644bd3f14cb.nix && nix-collect-garbage -d
#8 sha256:b14288120fda49c3952311baf2b490fed38e5c18b07a41507a8fa40b078b7061
#8 CACHED
#9 [stage-0 5/10] RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile
#9 sha256:12dcf6a42bf1344db5b7a02483f2b846eaf2f6bd1e5f24337f79a8189bc2ff93
#9 DONE 0.4s
#10 [stage-0 6/10] COPY . /app/.
#10 sha256:ce0a407cd50a1ccbe3be23e8717eb5b1978e54736f3716257765a0c50bc6ff1f
#10 DONE 0.1s
#11 [stage-0 7/10] RUN --mount=type=cache,id=s/b947d48a-6811-4bd7-be53-d870d96fde71-/root/npm,target=/root/.npm npm ci
#11 sha256:292fe72abf96a75827c016a9bb758e94e0a7fc5724f193e1c1830ac7b3ac5920
#11 0.730 npm WARN config
production Use `--omit=dev` instead.
#11 1.915 npm ERR! code ERESOLVE
#11 1.919 npm ERR! ERESOLVE could not resolve
#11 1.919 npm ERR!

it was a cors error, just needed to add these cookie options.
{
httpOnly: true,
secure: true,
sameSite: 'none',
}

Related

APK installation openssh | network error (check Internet connection and firewall)

I am behind Proxy and cannot hit to apk default repository. I have to go through a corporate repository, which is a snapshot of APK.
I ran this command:
[stage-1 3/12] RUN apk add openssh --repository=https://artifactory.internal.xyz/alpine-cache/v3.13/main/:
and I can see that https://artifactory.internal.xyz/alpine-cache/v3.13/main/ has x86_64/APKINDEX.tar.gz
But still , for whatever reason, it is still going to https://dl-cdn.alpinelinux.org/**
#7 0.491 fetch https://artifactory.internal.xyz/alpine-cache/v3.13/main/x86_64/APKINDEX.tar.gz
#7 3.601 fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/main/x86_64/APKINDEX.tar.gz
#7 24.75 ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.13/main: network error (check Internet connection and firewall)
#7 24.80 fetch https://dl-cdn.alpinelinux.org/alpine/v3.13/community/x86_64/APKINDEX.tar.gz
#7 45.96 ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.13/community: network error (check Internet connection and firewall)
#7 46.26 (1/7) Installing openssh-keygen (8.4_p1-r3)
#7 67.47 (2/7) Installing libedit (20191231.3.1-r1)
#7 67.47 ERROR: openssh-keygen-8.4_p1-r3: network error (check Internet connection and firewall)
What could be wrong here?
I am following ssh installation through a docker.
https://learn.microsoft.com/en-us/azure/app-service/configure-custom-container?pivots=container-linux#enable-ssh

ERROR: The certificate of 'dl.eff.org' is not trusted

I'm studying about docker, node and graphql and would like to make my project available in HTTPS.
I found this tutorial (https://techsparx.com/nodejs/docker/express-https.html) that explains how to do this, but I ran into an error and couldn't find a solution that works.
Building certbot
[+] Building 2.8s (9/11)
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 840B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/debian:jessie 1.9s
=> [auth] library/debian:pull token for registry-1.docker.io 0.0s
=> [1/7] FROM docker.io/library/debian:jessie#sha256:32ad5050caffb2c7e969dac873bce2c370015c2256ff984b70c1c08b3a2816a0 0.0s
=> CACHED [2/7] RUN apt-get update && apt-get install -y cron bash wget 0.0s
=> CACHED [3/7] RUN mkdir -p /webroots/bgl8700.com.br/.well-known /scripts 0.0s
=> CACHED [4/7] WORKDIR /scripts 0.0s
=> ERROR [5/7] RUN wget https://dl.eff.org/certbot-auto 0.7s
------
> [5/7] RUN wget https://dl.eff.org/certbot-auto:
#11 0.347 converted 'https://dl.eff.org/certbot-auto' (ANSI_X3.4-1968) -> 'https://dl.eff.org/certbot-auto' (UTF-8)
#11 0.347 --2021-10-24 20:20:12-- https://dl.eff.org/certbot-auto
#11 0.361 Resolving dl.eff.org (dl.eff.org)... 151.101.176.201, 2a04:4e42:2a::201
#11 0.569 Connecting to dl.eff.org (dl.eff.org)|151.101.176.201|:443... connected.
#11 0.640 ERROR: The certificate of 'dl.eff.org' is not trusted.
#11 0.640 ERROR: The certificate of 'dl.eff.org' has expired.
------
executor failed running [/bin/sh -c wget https://dl.eff.org/certbot-auto]: exit code: 5
ERROR: Service 'certbot' failed to build : Build failed
This is the Dockerfile:
FROM debian:jessie
# Install cron, certbot, bash, plus any other dependencies
RUN apt-get update \
&& apt-get install -y cron bash wget
RUN mkdir -p /webroots/bgl8700.com.br/.well-known /scripts
WORKDIR /scripts
RUN wget https://dl.eff.org/certbot-auto
RUN chmod a+x ./certbot-auto
# Run certbot-auto so that it installs itself
RUN /scripts/certbot-auto -n certificates
# /webroots/DOMAIN.TLD/.well-known/... files go here
VOLUME /webroots
VOLUME /etc/letsencrypt
# This installs a Crontab entry which
# runs "certbot renew" on several days of each week at 03:22 AM
#
# RUN echo "22 03 * * 2,4,6,7 root /scripts/certbot-auto renew" >/etc/cron.d/certbot
CMD [ "cron", "-f" ]
This is the register:
#!/bin/sh
/scripts/certbot-auto certonly --webroot -w /webroots/$1 -d $1
Folder Structure:
certbot/
- Dockerfile
- register
You need to take a closer look at the SSL certificate that is used in your setup. After all you have the messages
#11 0.640 ERROR: The certificate of 'dl.eff.org' is not trusted.
#11 0.640 ERROR: The certificate of 'dl.eff.org' has expired.
So check where in your process the certificate is created - and if it is not, then you need to add that part.

Chrome Error when running command yarn start

I am not aware of the technology used in this git repo but just trying to follow steps that are given by creator on https://github.com/paulmaunders/delivery-slot-bot
I have a windows machine and installed VMware player then Kali on it. Downloaded the repo and installed NPM in kali. When i run the command "Yarn Start" it is giving me the below error. I downloaded chrome and installed too but no joy. Any advice how to fix this would be greatly appreciated.
I have used Kali a bit so have some knowledge of Linux but cant figure this one out.
Thanks in advance
kali#kali:~/Downloads/delivery-slot-bot-master/delivery-slot-bot$ yarn start
yarn run v1.22.4
$ node ./src/index.js
index.js
Runs one-off
Options:
--version Show version number [boolean]
--help Show help [boolean]
Error: Failed to launch chrome!
[0421/142758.038038:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x564e68efe879 base::debug::CollectStackTrace()
#1 0x564e68e5bc63 base::debug::StackTrace::StackTrace()
#2 0x564e68e70013 logging::LogMessage::~LogMessage()
#3 0x564e6a60a95e service_manager::ZygoteHostImpl::Init()
#4 0x564e68a9fadc content::ContentMainRunnerImpl::Initialize()
#5 0x564e68aeb72c service_manager::Main()
#6 0x564e68a9e0b1 content::ContentMain()
#7 0x564e68aea99d headless::(anonymous namespace)::RunContentMain()
#8 0x564e68aea70b headless::HeadlessShellMain()
#9 0x564e6687b1b8 ChromeMain
#10 0x7f92b55efbbb __libc_start_main
#11 0x564e6687b02a _start
Received signal 6
#0 0x564e68efe879 base::debug::CollectStackTrace()
#1 0x564e68e5bc63 base::debug::StackTrace::StackTrace()
#2 0x564e68efe401 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7f92b7a76520 <unknown>
#4 0x7f92b5603081 gsignal
#5 0x7f92b55ee535 abort
#6 0x564e68efd265 base::debug::BreakDebugger()
#7 0x564e68e70461 logging::LogMessage::~LogMessage()
#8 0x564e6a60a95e service_manager::ZygoteHostImpl::Init()
#9 0x564e68a9fadc content::ContentMainRunnerImpl::Initialize()
#10 0x564e68aeb72c service_manager::Main()
#11 0x564e68a9e0b1 content::ContentMain()
#12 0x564e68aea99d headless::(anonymous namespace)::RunContentMain()
#13 0x564e68aea70b headless::HeadlessShellMain()
#14 0x564e6687b1b8 ChromeMain
#15 0x7f92b55efbbb __libc_start_main
#16 0x564e6687b02a _start
r8: 0000000000000000 r9: 00007ffde55c0d60 r10: 0000000000000008 r11: 0000000000000246
r12: 00007ffde55c2028 r13: 00007ffde55c1008 r14: 00007ffde55c1008 r15: 00007ffde55c1020
di: 0000000000000002 si: 00007ffde55c0d60 bp: 00007ffde55c0fb0 bx: 00007f92b5783840
dx: 0000000000000000 ax: 0000000000000000 cx: 00007f92b5603081 sp: 00007ffde55c0d60
ip: 00007f92b5603081 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
at onClose (/home/kali/Downloads/delivery-slot-bot-master/delivery-slot-bot/node_modules/puppeteer/lib/Launcher.js:348:14)
at Interface.helper.addEventListener (/home/kali/Downloads/delivery-slot-bot-master/delivery-slot-bot/node_modules/puppeteer/lib/Launcher.js:337:50)
at Interface.emit (events.js:203:15)
at Interface.close (readline.js:397:8)
at Socket.onend (readline.js:173:10)
at Socket.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentat
ion about this command.
The thing with kali is that everytime you're logged in as the root user and everything you execute will run as root as well. But chrome knows that it's not a good idea to run it as root so it says no to you.
As the error message says, you can add the --no-sandbox to the launch option and make it run as root. However, this is not a very good idea. Running non-system applications or processes, including the ones with graphics, is not a good idea in general.
It's better that you switch to a non-root account and do all your web devs there, or just switch to a normal distro like Ubuntu.

"Gradle task assembleDebug failed" using VsCode and either ADV or real device

The VsCode's debug mode isn't launching the app any more, eiter through the AVD or a real android device. Used to working perfectly on both until yesterday.
I am getting an error
Launching lib\main.dart on Android SDK built for x86 in debug mode...
Gradle task assembleDebug failed with exit code 1
Exited (sigterm)
I ran flutter doctor -v
[√] Flutter (Channel stable, v1.0.0, on Microsoft Windows [version 10.0.17134.523], locale fr-FR)
• Flutter version 1.0.0 at F:\flutter_src
• Framework revision 5391447fae (6 weeks ago), 2018-11-29 19:41:26 -0800
• Engine revision 7375a0f414
• Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)
[√] Android toolchain - develop for Android devices (Android SDK 28.0.3)
• Android SDK at F:\Android_sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• ANDROID_HOME = F:\Android_sdk
• Java binary at: F:\Android_src\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
• All Android licenses accepted.
[√] Android Studio (version 3.2)
• Android Studio at F:\Android_src
• Flutter plugin version 31.3.1
• Dart plugin version 181.5656
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[√] Connected device (1 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)
I have to say that I have absolutely no idea of what went wrong.
I don't think it is code related, has I haven't made huge impacting change to my project. Other than that error inside the debug console, it isn't throwing me anything else.
Edit
Flutter run -v
[ +128 ms] executing: [F:\flutter_src\] git rev-parse --abbrev-ref --symbolic #{u}
[ +245 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic #{u}
[ ] origin/stable
[ ] executing: [F:\flutter_src\] git rev-parse --abbrev-ref HEAD
[ +73 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[ +2 ms] stable
[ ] executing: [F:\flutter_src\] git ls-remote --get-url origin
[ +88 ms] Exit code 0 from: git ls-remote --get-url origin
[ ] https://github.com/flutter/flutter.git
[ ] executing: [F:\flutter_src\] git log -n 1 --pretty=format:%H
[ +99 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[ ] 5391447fae6209bb21a89e6a5a6583cac1af9b4b
[ ] executing: [F:\flutter_src\] git log -n 1 --pretty=format:%ar
[ +80 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[ ] 6 weeks ago
[ +1 ms] executing: [F:\flutter_src\] git describe --match v*.*.* --first-parent --long --tags
[ +253 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[ ] v1.0.0-0-g5391447fa
[ +308 ms] executing: F:\Android_sdk\platform-tools\adb devices -l
[+4275 ms] Exit code 0 from: F:\Android_sdk\platform-tools\adb devices -l
[ ] List of devices attached
[ +19 ms] No connected devices.
[ +20 ms] "flutter run" took 4 413ms.
#0 throwToolExit (package:flutter_tools/src/base/common.dart:26:3)
#1 RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:249:7)
<asynchronous suspension>
#2 FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:379:11)
<asynchronous suspension>
#3 FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:335:33)
<asynchronous suspension>
#4 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#5 _rootRun (dart:async/zone.dart:1124:13)
#6 _CustomZone.run (dart:async/zone.dart:1021:19)
#7 _runZoned (dart:async/zone.dart:1516:10)
#8 runZoned (dart:async/zone.dart:1463:12)
#9 AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#10 FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:326:20)
#11 CommandRunner.runCommand (package:args/command_runner.dart:196:27)
<asynchronous suspension>
#12 FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:401:21)
<asynchronous suspension>
#13 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#14 _rootRun (dart:async/zone.dart:1124:13)
#15 _CustomZone.run (dart:async/zone.dart:1021:19)
#16 _runZoned (dart:async/zone.dart:1516:10)
#17 runZoned (dart:async/zone.dart:1463:12)
#18 AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#19 FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:361:19)
<asynchronous suspension>
#20 CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:111:29)
#21 new Future.sync (dart:async/future.dart:224:31)
#22 CommandRunner.run (package:args/command_runner.dart:111:11)
#23 FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:241:18)
#24 run.<anonymous closure> (package:flutter_tools/runner.dart:60:20)
<asynchronous suspension>
#25 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#26 _rootRun (dart:async/zone.dart:1124:13)
#27 _CustomZone.run (dart:async/zone.dart:1021:19)
#28 _runZoned (dart:async/zone.dart:1516:10)
#29 runZoned (dart:async/zone.dart:1463:12)
#30 AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#31 runInContext (package:flutter_tools/src/context_runner.dart:43:24)
<asynchronous suspension>
#32 run (package:flutter_tools/runner.dart:51:10)
#33 main (package:flutter_tools/executable.dart:51:9)
<asynchronous suspension>
#34 main (file:///E:/b/build/slave/Windows_Flutter_Packaging/build/archive/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#35 _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:287:32)
#36 _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)
EDIT 2 : Thanks to Siavash for speaking about "flutter clean".
It solved the problem !
Still curious about the "why" of this problem tho.
Thank to Siavash : flutter clean, from inside the project folder, solved the issue (or simply by using the VSCode terminal).
here I have a answer. See steps below:-
1- Go to your flutter folder where you saved, go and run the 'flutter_console.bat' file. a console will be open.
2- Type "flutter doctor".:-
3- It will show all the problems in your flutter setup. In my case you can see:-
C:\Users\M A Hafeez>flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 1.22.5, on Microsoft Windows [Version 10.0.19042.685], locale en-US)
flutter_run
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
X No Java Development Kit (JDK) found; You must have the environment variable JAVA_HOME set and the java binary in your PATH. You can download the JDK from https://www.oracle.com/technetwork/java/javase/downloads/.
[!] Android Studio (not installed)
[√] VS Code (version 1.52.1)
[√] Connected device (1 available)
! Doctor found issues in 2 categories.
Basically my error was about Java, that I have no installed before facing this error.
Hope this will be helpful. :)
Enjoy Coding

Taiko throws Error: Failed to launch chrome No usable sandbox

I am trying to run Gauge/Taiko however I am getting an error just at the very beginning when I only issue openBrowser() command. My OS is Debian 9 Stretch and I use local Gauge/Taiko installation.
The error seems to suggest I need to update my kernel - do I really need that? I would hope Taiko includes appropriate build of chromium, especially that https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux_suid_sandbox.md states ate the very first line that "page is mostly out-of-date" and it looks like a set of instructions for installation from source rather than using provided packages.
I'd appreciate any help, I am also happy for a suggestion of Taiko's preferred distro ;]
$ npm --version
6.4.1
$ ./node_modules/.bin/taiko
Version: 0.3.0 (Chromium:71.0.3563.0)
Type .api for help and .exit to quit
> openBrowser()
✘ Error: Failed to launch chrome!
[12296:12296:1105/121525.023333:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x55e22767dcac base::debug::StackTrace::StackTrace()
#1 0x55e2275f7670 logging::LogMessage::~LogMessage()
#2 0x55e228afb050 service_manager::ZygoteHostImpl::Init()
#3 0x55e2272c0d7e content::ContentMainRunnerImpl::Initialize()
#4 0x55e2272f43e8 service_manager::Main()
#5 0x55e2272bf5c1 content::ContentMain()
#6 0x55e2255ff1b3 ChromeMain
#7 0x7fc5c46222e1 __libc_start_main
#8 0x55e2255ff02a _start
Received signal 6
#0 0x55e22767dcac base::debug::StackTrace::StackTrace()
#1 0x55e22767d821 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7fc5ca7b10c0 <unknown>
#3 0x7fc5c4634fff gsignal
#4 0x7fc5c463642a abort
#5 0x55e22767c645 base::debug::BreakDebugger()
#6 0x55e2275f7ae8 logging::LogMessage::~LogMessage()
#7 0x55e228afb050 service_manager::ZygoteHostImpl::Init()
#8 0x55e2272c0d7e content::ContentMainRunnerImpl::Initialize()
#9 0x55e2272f43e8 service_manager::Main()
#10 0x55e2272bf5c1 content::ContentMain()
#11 0x55e2255ff1b3 ChromeMain
#12 0x7fc5c46222e1 __libc_start_main
#13 0x55e2255ff02a _start
r8: 0000000000000000 r9: 00007ffde9ca88e0 r10: 0000000000000008 r11: 0000000000000246
r12: 00007ffde9ca90f8 r13: 000000000000016d r14: 00007ffde9ca9100 r15: 00007ffde9ca9108
di: 0000000000000002 si: 00007ffde9ca88e0 bp: 00007ffde9ca8b20 bx: 0000000000000006
dx: 0000000000000000 ax: 0000000000000000 cx: 00007fc5c4634fff sp: 00007ffde9ca8958
ip: 00007fc5c4634fff efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
, run `.trace` for more info.
>
If you loading fully trusted site in the browser, alternatively you can also pass
'--no-sandbox', '--disable-setuid-sandbox' args to openBrowser like
await openBrowser({args:['--no-sandbox', '--disable-setuid-sandbox']})
Someone faced similar problem
https://github.com/iridium-browser/tracker/issues/208#issuecomment-395619508
Enabling unprivileged namespaces solved the issue.
Quoting solution:
# echo kernel.unprivileged_userns_clone=1 > /etc/sysctl.d/00-local-userns.conf
# sysctl --system

Resources