Error in dev environment in Steam OS

I'm trying to set up a development environment to contribute to Heroic Launcher on a Steam Deck. I followed the instructions on the readme. When running the dev container inside VSCode or on the terminal, I'm getting the following error.

error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory. If I run

yarn start

yarn start

yarn start

yarn start outside the container, Heroic launches without any problem. What should I do to install this missing dependency inside the dev container? Anybody got any tips on setting this up on steam os?

Node version: v18.12.1
OS version: Linux steamdeck 5.13.0-valve36-1-neptune

brilliant-lime•12/30/22, 1:27 PM

I think the dev container needs the missing libs

brilliant-lime•12/30/22, 1:27 PM

Or docker can not run on ste deck

brilliant-lime•12/30/22, 1:27 PM

Is there docker for flatpak?

brilliant-lime•12/30/22, 1:28 PM

@FlavioF34rn you developed on steam deck right?

moderate-tomato•12/30/22, 1:29 PM

yes but not using a container

moderate-tomato•12/30/22, 1:29 PM

I just installed node using nvm, everything locally

moderate-tomato•12/30/22, 1:29 PM

and was fine

inadequate-blushOP•12/30/22, 1:31 PM

@FlavioF34rn That's good to know. I just wanted make sure to isolate the dev version from the stable Heroic installation. (Not to mess up my current heroic installation as suggested in the readme)

brilliant-lime•12/30/22, 1:32 PM

If you have heroic as flatpak you can't mess up things. At least on my PC i do it like this and no problems.

brilliant-lime•12/30/22, 1:32 PM

heroic flatpak stores configs and stuff in different folders

brilliant-lime•12/30/22, 1:33 PM

via yarn start everything should go to ~/.config/heroic~/.config/heroic

brilliant-lime•12/30/22, 1:33 PM

flatpak heroic shouldbe in ~/.var/app/com.heroicgameslauncher.hgl/config/heroic~/.var/app/com.heroicgameslauncher.hgl/config/heroic

Bbrilliant-lime Or docker can not run on ste deck

inadequate-blushOP•12/30/22, 1:34 PM

@Nocccer thanks for the suggestion! I'm using podman instead of docker on steamdeck but the commands work almost the same. I can enter the container without any problem. but yarn start inside the container fails with the above error

Bbrilliant-lime If you have heroic as flatpak you can't mess up things. At least on my PC i do i...

inadequate-blushOP•12/30/22, 1:34 PM

Great! this is good to know. thank you very much for the clarification

brilliant-lime•12/30/22, 1:35 PM

I think podman misses some libs then. Because the Dockerfile pulls a arch image

brilliant-lime•12/30/22, 1:35 PM

Don't know how podman works

brilliant-lime•12/30/22, 1:35 PM

You probably need a linux image and install nodejs, npm. Via npm you can install yarn

inadequate-blushOP•12/30/22, 1:38 PM

Yeah. I'll stick with the regular environment for now then without a container.

brilliant-lime•12/30/22, 1:39 PM

I think you need to find out how to install dependencies inside a podman instance

brilliant-lime•12/30/22, 1:40 PM

if pacman works you can just install the missing libs like nodejs

inadequate-blushOP•12/30/22, 1:40 PM

(Just to let you know, replacing dockerdocker with podmanpodman in the commands in the readme got me some distance e.g. podman run -it -v ./:/tmp/heroic localhost/heroicdevcontainer:latestpodman run -it -v ./:/tmp/heroic localhost/heroicdevcontainer:latest.I can see node, yarn, npm is all there inside the container.)

inadequate-blushOP•12/30/22, 1:41 PM

only missing thing seems to be libnss3 somehow

brilliant-lime•12/30/22, 1:41 PM

just install it via pacman

brilliant-lime•12/30/22, 1:42 PM

i don't know if you use the Dockerfile but you could adapt it or you write a new podman file which describe your container looks like

brilliant-lime•12/30/22, 1:44 PM

Seems like podman can use Dockerfile. So you could add nssnss in the Dockerfile

brilliant-lime•12/30/22, 1:44 PM

RUN pacman -Syyu --noconfirm && pacman -S nodejs npm yarn nss --noconfirm RUN pacman -Syyu --noconfirm && pacman -S nodejs npm yarn nss --noconfirm

inadequate-blushOP•12/30/22, 1:46 PM

Thanks. I'm trying to just enter the container and install it first to make sure problem goes away, without modifying the dockerfile just yet

brilliant-lime•12/30/22, 1:46 PM

If you solved it you could write a podman config file and add steps to run devcontainer for podman in the readme

brilliant-lime•12/30/22, 1:47 PM

Could be your first contribution

inadequate-blushOP•12/30/22, 2:14 PM

Thanks @Nocccer for your help! I ended up installing all these packages at the end as responses to the errors I was getting.. pacman -Sy at-spi2-core libcups libdrm gtk3 alsa-lib nsspacman -Sy at-spi2-core libcups libdrm gtk3 alsa-lib nss Even then it ended up diving me this error:

inadequate-blushOP•12/30/22, 2:16 PM

 built in 119ms.
[1795:0100/000000.581525:ERROR:zygote_linux.cc(649)] write: Broken pipe (32)
[1796:0100/000000.598227:ERROR:zygote_linux.cc(649)] write: Broken pipe (32)
[1797:1230/140945.444448:ERROR:ozone_platform_x11.cc(240)] Missing X server or $DISPLAY
[1797:1230/140945.444481:ERROR:env.cc(255)] The platform failed to initialize.  Exiting.
Done in 19.59s.

 built in 119ms.
[1795:0100/000000.581525:ERROR:zygote_linux.cc(649)] write: Broken pipe (32)
[1796:0100/000000.598227:ERROR:zygote_linux.cc(649)] write: Broken pipe (32)
[1797:1230/140945.444448:ERROR:ozone_platform_x11.cc(240)] Missing X server or $DISPLAY
[1797:1230/140945.444481:ERROR:env.cc(255)] The platform failed to initialize.  Exiting.
Done in 19.59s.

inadequate-blushOP•12/30/22, 2:17 PM

So I'm going to stop pursuing the podman path for now and stick with the regular environment. Just noting this here for posterity

Error in dev environment in Steam OS

Similar Threads

Similar Threads

Similar Threads