Scaling or pre-sizing images about container2wasm HOT 9 OPEN

Is this duplication of #191 ?

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

from container2wasm.

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

from container2wasm.

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?

from container2wasm.

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

from container2wasm.

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/

from container2wasm.

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

from container2wasm.

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

from container2wasm.

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!

from container2wasm.

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.

from container2wasm.