Skip to content

Fix problem with booting server from Docker image#3

Closed
nazgu1 wants to merge 1 commit intomohitgauniyal:mainfrom
nazgu1:main
Closed

Fix problem with booting server from Docker image#3
nazgu1 wants to merge 1 commit intomohitgauniyal:mainfrom
nazgu1:main

Conversation

@nazgu1
Copy link
Copy Markdown
Contributor

@nazgu1 nazgu1 commented Mar 17, 2026

Once again.

Today I debugged the problem more, as I spotted that with previous solutions DATA and UPLOAD paths are ignored. bin/instbyte.js sets env variables, so it overrides env from Dockerfile.

There was one env var (INSTBYTE_BOOT) missing in docker file, so the sever hangs before start.

Should be fixed now and server should honour paths set in docker command or compose file.

@mohitgauniyal
Copy link
Copy Markdown
Owner

Hey, you identified the right bug,
bin/instbyte.js was unconditionally overwriting env vars set in Docker. Appreciate you digging into it.

The concern with your approach is that routing Docker through node server/server.js directly bypasses bin/instbyte.js which handles directory creation on startup.. skipping it could cause crashes on fresh volumes.

I've fixed the underlying issue directly in bin/instbyte.js instead — env vars already set in the environment are now respected and not overwritten. Just pushed to main.

If you want the test:watch script added separately, happy to take that as a standalone PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants