Skip to content

Disk not mounted properly with cloud-init #194

@DesmondH0

Description

@DesmondH0

First of all, thanks for the handling GCP container VM deprecation for us 🥇

We are replacing our Atlantis deployment with latest commit and found out the VM with persistent disk do not mount properly.
Although contents exist on /mnt/disks/gce-containers-mounts/gce-persistent-disks/atlantis-disk-0, the VM is actually seeing /mnt/disks path with 256K only due to tmpfs
Image

So once the atlantis container mounted the disk, it could failed with error below with any operations:

fatal: write error: No space left on device
fatal: fetch-pack: invalid index-pack output
: exit status 128

As a workaround for now, I had mounted the disk during startup_script, just wondering if this is an expected behaviour?

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageWaiting for first response or review from a maintainer

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions