ktock/container2wasm

Scaling or pre-sizing images

Cinemacloud opened this issue · 9 comments

How do I resize or configure the size at build? I didn't see much mention of that but perhaps entirely a docker concern and question?

ktock commented

Is this duplication of #191 ?

EDIT: I've added some comments on that thread.

More or less but curious how I can at least tweak storage size (through Docker?) before its implemented in c2w itself.. or not possible?

ktock commented

tweak storage size (through Docker?)

Could you elaborate what "storage" means? The storage usage by docker during build? Or the output Wasm image size? Or the disk size of the container(VM) running on browser?

yes, practically I was just updating the packages and it quickly ran out of space and stopped working.

ktock commented

We rely on docker build for generating wasm images so it sounds like Docker's concern. If it's ok to remove your Docker build cache, Docker provides docker builder prune for removing build cache and increasing free space. https://docs.docker.com/engine/reference/commandline/builder_prune/

So c2w has no practical limits other than Docker prescribes via images and containers?

ktock commented

Yes. If needed, we can fix c2w to optionally use some flags of docker build for limiting resource usage: https://docs.docker.com/engine/reference/commandline/build/#options

That would be awesome or show me how I can do it in few steps I plan to use this in a big project poc, thanks!

Just curious if you were able to give hardware scaling params into build yet and also could you put together a demo using Neko browser which is docker based already.