You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After fix above two problem, container started up. However, accessing the exposed port don't get respond data. The log of the container is empty.
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
886fc58021f0 yoo "/entrypoint.sh" 21s ago Up 20s 0.0.0.0:32771->8080/tcp yoo
$ curl localhost:32771
curl: (52) Empty reply from server
$ docker logs yoo
(empty)
The text was updated successfully, but these errors were encountered:
I quick walked thought the code. The idea of downloading k8s binaries from intranet HTTP server during installation and starting services via cloudinit during OS start up is pretty clear. Even though there are still many questionable parts. Like why only production-central.ejs and production-worker.ejs content k8s units, and what's the purpose of yml_fleet folder.
Got several issues when trying to setup the app via the Dockerfile in repo.
1) entrypoint.sh do not have executable permission
Put a
RUN chmod +x /entrypoint.sh
in Dockerfile will fix it.2)
npm install
is necessaryI see there is a commented
npm install
in Dockerfile, it's necessary, otherwise nodejs app won't start up.3) App not working without error log
After fix above two problem, container started up. However, accessing the exposed port don't get respond data. The log of the container is empty.
The text was updated successfully, but these errors were encountered: