Set up a git repository to store packet.net images
Categories
(Taskcluster :: Workers, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: wcosta, Unassigned)
References
Details
Packet.net doesn't provide a store for custom images. Instead, custom images must live in a git repo and you point to it through instance user data [1].
Each image is around 1.5GB large. Github doesn't allow such big files in the repo by default (but maybe a support request may solve that). We also have the option for gitlab (which is what I am using for tests) or a repo inside Mozilla infra.
Reporter | ||
Comment 1•6 years ago
|
||
:fubar, any way to talk to packet guys and see if they have a solution for storing custom images, or, if not, allow us to specify a URL to download images from?
Comment 2•6 years ago
|
||
I'll reach out to our rep and ask, though their support page doesn't leave me feeling hopeful. I'm a little surprised that they're using git(hub) to store their images; IME git is really terrible with large blobs like that.
Presuming that Packet doesn't have another option, I'd suggest AWS CodeCommit, which is git under the hood.
How many custom images do we currently have?
Reporter | ||
Comment 3•6 years ago
|
||
(In reply to Kendall Libby [:fubar] (he/him) from comment #2)
I'll reach out to our rep and ask, though their support page doesn't leave
me feeling hopeful. I'm a little surprised that they're using git(hub) to
store their images; IME git is really terrible with large blobs like that.
Things are a bit better since lfs was integrated into the core git.
Presuming that Packet doesn't have another option, I'd suggest AWS
CodeCommit, which is git under the hood.How many custom images do we currently have?
Currently, none (at least official images), but expect one with each version of docker-worker released.
Comment 4•6 years ago
|
||
Our packet rep didn't have much technical info to help, other than suggesting we could use a dedicated node for storage (though the custom image docs you linked still don't say how one would use that). I'd suggest reaching out to help@packet.net or open a ticket (https://support.packet.com/new-ticket).
Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•5 years ago
|
Description
•