Skip to content

Conversation

@3405691582
Copy link
Collaborator

Then plumb that through to the script. This means that logic on the golang side owns the knowledge of the mountpoint, and doesn't need to assume that it knows what the mountpoint is from the shell script.

@3405691582 3405691582 requested a review from ser-io December 4, 2025 19:34
sudo mount --bind /dev/ /mnt/image/dev
sudo mount --bind /dev/pts /mnt/image/dev/pts
sudo mount --bind /run /mnt/image/run
MOUNTPONT=$1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's update other tools: create_gce_x86_64_image, create_gce_x86_64_fixed_kernel using this script as well.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These will require more wide refactors. I have however ensured that this mount script gets invoked correctly everywhere, though.

Then plumb that through to the script. This means that logic on the
golang side owns the knowledge of the mountpoint, and doesn't need to
assume that it knows what the mountpoint is from the shell script.

For now, this is only done on the `gce_install_cuttlefish_packages`
command.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants