Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • alpine-ec2-ami alpine-ec2-ami
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • cloudcloud
  • alpine-ec2-amialpine-ec2-ami
  • Issues
  • #90
Closed
Open
Issue created Nov 08, 2020 by Jake Buchholz Göktürk@tomalokOwner

Bootload Directly via EFI_STUB?

(As reported in https://github.com/mcrute/tiny-ec2-bootstrap/issues/15 by @tsarna)

Problem is that the bootloader on x86_64 is installed on the raw EBS volume (allowing resize2fs to expand to the full volume size) vs. a partition on aarch64, which restricts resize2fs to the size of root partition, as defined by the AMI image.

Possible solutions to be applied here (instead of https://github.com/mcrute/tiny-ec2-bootstrap)...

  • install grub bootloader on raw EBS volume instead of partitioning (if that's even possible)
  • perhaps switch to u-boot bootloader. There is apparently some compatibility with syslinux -- https://linux-sunxi.org/U-Boot#Booting_with_extlinux.conf -- switching would likely reduce the footprint of the aarch64 AMI.
Edited Dec 27, 2021 by Jake Buchholz Göktürk
Assignee
Assign to
Time tracking