However, I'd rather not have to keep doing this every couple of years as things grow, so I'd go with 1GB.Īs the OEM partition is not currently part of the update payload, a change in the size of the partition wouldn't interfere with updates. If we think that's too much, we could go with 512MB, which would still allow us to ship the needed AWS tools and leave some space for growth. This also means that the minimum disk size would grow by those same ~900MB. The main difference with the current state would be that after the image gets unpacked and the root disk resized, there would be ~900MB less in the root partition. As the size of the downloaded image only includes actual data, it would only grow in the cases where we would ship more stuff (like AWS). Going for 1GB for the OEM partition sounds sensible given the current state. We should have a bigger OEM partition so that we are not limited in the tools that we want to ship. This is affecting AWS in particular ( #107) Users can run those tools as containers, but it means that running those tools requires an internet connection. This means that if we're trying to ship big OEM tools, we can't. Currently we are limited to shipping a maximum of 128MB in the OEM partition.
0 kommentar(er)
