Why there is no more /dev/sdb on ubuntu runners running private repo workflows ?
Open
Nobody has claimed this yet.
bug
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Hello there,
Since few days, I observe this behaviour:
- on ubuntu public runners running public-repo workflows, there still is the secondary 75 GB disk on
/dev/sdb:
$ cat /etc/issue*
Ubuntu 22.04.5 LTS
$ fdisk -l
[...]
Disk /dev/sdb: 75 GiB, 80530636800 bytes, 157286400 sectors
Disk model: Virtual Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8c7bf172
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 157284351 157282304 75G 7 HPFS/NTFS/exFAT
- While on runners running "private" workflows, that's to say public runners running private-repo workflows, there is no more this secondary disk
/dev/sdb(only/dev/sda). So we now have limited disk in that case.
Do you also observe this ?
Can you put again this secondary disk for private-repo workflows ?
Cheers!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the fdisk -l output on Ubuntu public runners handling public-repository and private-repository workflows. Trace the runner provisioning behavior for those workflows and confirm whether the missing /dev/sdb is intentional; done means restoring the secondary disk for private workflows or documenting the expected limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions, ubuntu
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100