Disk layout of Alpine Linux appliances
See original GitHub issueDisk layout of the Alpine appliances is not ideal, should be just single partition https://github.com/OpenNebula/marketplace/issues/8#issuecomment-438371343:
label: dos
label-id: 0x512515ea
device: /dev/loop1
unit: sectors
/dev/loop1p1 : start= 2048, size= 204800, type=83, bootable
/dev/loop1p2 : start= 206848, size= 262144, type=82
/dev/loop1p3 : start= 468992, size= 579584, type=83
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Setting up disks manually - Alpine Linux Wiki
This requires some manual steps, as long as the setup-scripts auto-detect usable partitions only on *removable* devices (not internal harddisks).
Read more >Disk layout of Alpine Linux appliances · Issue #5616 - GitHub
Disk layout of the Alpine appliances is not ideal, should be just single partition ...
Read more >Linux Container - Proxmox VE
Containers are a lightweight alternative to fully virtualized machines (VMs). They use the kernel of the host system that they run on, ...
Read more >System Installation — OpenZFS documentation - GitHub Pages
Partition the disks: · Probe new partitions: · Create boot partition: · Create root pool: · This section implements dataset layout as described...
Read more >Building 64bit alpine linux GNS3 FRRouting appliance
This FRRouting installation needs only 100 MB of disk space. ... root # apk add frr sudo mtr agetty ifupdown-ng alpine-baselayout ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For Alpine, we build the images from scratch and we can (more or less) modify the process to match the general user requirements. That’s why we have this ticket.
For Ubuntu, we reuse their cloud images https://cloud-images.ubuntu.com/ and only customize them to work with the OpenNebula. Those images aren’t perfect (different disk layout or filesystems), but all the functionality for running inside the OpenNebula cloud is there. There are no plans to modify this process right now.
GPT is supported by the growpart tool, no problem with it.
BTW, I wrote a generator opennebula-images from the official Dockerfiles, unfortunately I have no time to finish it.
The sources can be found here, take a look: https://github.com/kvaps/opennebula-images/tree/da5bcbadbe2915167ef74fde7166ff4d75fb1151/new