The same is going one when I try to run shadow-cljs start on Docker image https://github.com/theasp/docker-clojurescript-nodejs locally. You can reproduce it from your project directory using

docker run --rm -v ${PWD}:/home/my-project -w="/home/my-project" theasp/clojurescript-nodejs:latest npx shadow-cljs start

why are you using start in a CI environment?

@thheller I would like to use https://github.com/lambdaisland/kaocha-cljs2 to run tests and I need somehow to serve the compiled tests with shadow-cljs, so I have decided to use shadow-cljs server for that. I am not sure if it is the best choice. I would appreciate a better advice on that if you have

hmm I don't know anything about kaocha or how it runs tests unfortunately

you could maybe run the tests via https://shadow-cljs.github.io/docs/UsersGuide.html#clj-run

Actually what I need is to serve the complied directory with lambdaisland.chui.remote to be preloaded. And shadow-cljs server looks ideal. I could try to look for another way to achieve the same. But do you have any idea why it doesn’t work on Docker? Is it expected or can I log the issue in GitHub for that?

I don't have a clue why it wouldn't work. maybe the logfiles created in the .shadow-cljs/ dir provide some clues? I'm not capable of debugging docker issues. if server works fine I'd assume start to work as well since the only thing it does is detach to process into the background.

let me actually check if shadow-cljs server works inside Docker. I haven’t checked it separately

@thheller when I am using shadow-cljs server with local docker I get a project specific error (out of scope for my question). But it seems shadow-cljs start hanging when errors occur, is it possible?

how does it fail? could certainly affect start yes

shadow-cljs server failed (actually process just ends) during fetching lein private dependencies because of luck of permissions. During shadow-cljs start it just shows dots

yeah with start all logging goes into the log files in .shadow-cljs/server.stdout.log or server.stderr.log

@thheller thanks for you advices, they helped me to find root cause of the problem. I will create an issue in GitHub for use case that start is hanging when error occurs during start up if you don’t mind. My root issue on Jenkins was that jks ssl certificate which we use for local environment was not committed and I still not sure is it a good idea to commit it. Is it possible somehow to force shadow-cljs to ignore ssl certificate if it is not found instead of throwing exception?

if the cert is not found ssl won't work? or do you not need that to work?

I don’t need that to work. I need SSL for local server but not when I run tests

hmm yeah I guess there should be an option to disable that but for CI you could just write a simple script that just deletes the :ssl config from shadow-cljs.edn before actually starting it

Option will be better, but I try to write something in meanwhile

(require '[ :as io])
(require '[clojure.edn :as edn])
(let [file (io/file "shadow-cljs.edn")]
  (-> (slurp file)
      (edn/read-string)
      (dissoc :ssl)
      (as-> config
        (spit file (pr-str config)))))

if you have clojure installed on the CI system you can just put that into a script file and run it with that

or use something like babashka

thanks a lot. I’ll try

feel free to open issues about this. can't get to it now but maybe later