Open micressor opened 1 year ago
The dockerfile seems to use almost 30GB of temporary space to build the container.
Do you understand why?
I think it is due to the different build stages. As soon as the container is running and I run a clean up
podman system prune --all -f
the disk usage of podman is reduced to about 100mb (what the njump container/image) itself needs.
The dockerfile seems to use almost 30GB of temporary space to build the container.
It's best not to use containers if you don't have enough disk space, or try building them on a dedicated machine and deploying them on a node machine.
Just use the Go compiler or download a precompiled binary. Docker is a nuisance.
I can't tell. For me as an operator and not a developer, distribution packages or a container are a benefit ;-)
I cannot currently build njump on debian 10:
TAILWIND_DEBUG=true go run .
invalid go version '1.21.0': must match format 1.23
Long story short, the Dockerfile works, just needs a lot of temporary space.
The pre-compiled binary njump-v0.0.1-linux-amd64
seems to have a problem.
The layout is completely distorted.
According to the network analyzer, something from the tailwind bundle is not loading correctly.
The precompile binaries were indeed broken. They're fixed now in the new release. Thank you.
About Docker, we'll accept contributions that make the Docker build less wasteful in resources. I have no idea of how to do that myself.
To build locally unfortunately you need the latest Go version, I'll try to not force that as a requirement in the future.
The precompile binaries were indeed broken. They're fixed now in the new release. Thank you.
yes! Now it works - thanks a lot.
To build locally unfortunately you need the latest Go version, I'll try to not force that as a requirement in the future.
That would be very helpful - thanks.
i would be very happy about a podman/docker container that I can easily run.