# Fork Your Own image

**URL:** <https://universal-blue.discourse.group/t/fork-your-own-image/43>\
**Category:** Contributing\
**Created:** [November 12, 2023, 3:46am UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43 "2023-11-12T03:46:27Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\
**Post date:** [November 12, 2023, 3:46am UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/1 "2023-11-12T03:46:27Z")

</div>

## Making your own image by forking Bazzite, Bluefin, or Aurora

Sometimes you don’t want to make a whole new image from scratch, you just want to change some things without too much extra work. Sometimes it’s nicer to derive from images that more end-user focused like [Bazzite](https://github.com/ublue-os/bazzite), [Bluefin](https://github.com/ublue-os/bluefin), and [Aurora](https://getaurora.dev/).

## Using the Image template

Use the [**official template image**](https://github.com/ublue-os/image-template) to build off of to make your own custom Bazzite, Bluefin, or Aurora if preferred over forking the project.

## Use Cases

- You want to help development by being able to test your contributions prior to submiting to the community.
  - Hardware enablement, experimental features, confirming fixes ahead of merge

- You want to change out applications and other default choices but want to stick close to Bazzite/Bluefin to get improvements automatically
  - For example, Bluefin DX has Visual Studio baked into the image. If you want the rest of it but don’t use vscode you could replace it or remove it.
  - You need to layer something like VPN software that has to be on an image but you don’t want to maintain your own standalone image. (Deriving off of others is always easier, that’s why we made this project)
  - You want a personal-use image with config and software changes, but also want to benefit from work being completed upstream.

[`ublue-os/main`](https://github.com/ublue-os/main) are used to generate base images of everything, so are usually not good candidates for this unless you are familiar with git, containers, and GitHub Actions.

---

<div class="post-metadata">

**Author:** ![rik](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/rik/32/1099_2.png) [@rik](https://universal-blue.discourse.group/u/rik)\
**Post date:** [April 3, 2024, 9:07pm UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/2 "2024-04-03T21:07:37Z")

</div>

@j0rge I am a bit confused if this post is the authoritative guide on how to create a custom image? Even in this post there is reference to the `documentation/tinker` category, but I think with the new website there is no current way to access this `tinker` category?

[This post / video](https://universal-blue.discourse.group/t/fork-your-own-image/43) shows a very friendly way to get started with a custom image, but maybe that way isn’t kept up-to-date or supported now?

---

<div class="post-metadata">

**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\
**Post date:** [April 3, 2024, 9:08pm UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/3 "2024-04-03T21:08:15Z")

</div>

We’re working on new instructions, sorry this part’s kind of in limbo right now.

---

<div class="post-metadata">

**Author:** ![pawann](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@pawann](https://universal-blue.discourse.group/u/pawann)\
**Post date:** [April 4, 2024, 4:26am UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/4 "2024-04-04T04:26:53Z")

</div>

Much appreciated!, curiously waiting for the new instructions, please take your time 😄

---

<div class="post-metadata">

**Author:** ![rik](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/rik/32/1099_2.png) [@rik](https://universal-blue.discourse.group/u/rik)\
**Post date:** [April 4, 2024, 4:30pm UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/5 "2024-04-04T16:30:39Z")

</div>

I have found [https://blue-build.org/](https://blue-build.org/) which seems to piece together some of the confusion over where the prior documentation went to and why it was split off to this separate project. So the video I linked was using this method which isn’t aligned with uBlue’s current supported direction which is undergoing a re-write, as j0rge notes above.

---

<div class="post-metadata">

**Author:** ![pawann](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@pawann](https://universal-blue.discourse.group/u/pawann)\
**Post date:** [April 8, 2024, 8:09am UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/6 "2024-04-08T08:09:21Z")

</div>

Thanks for the info, I did however stumble upon bluebuild before but didn’t try it out. Did you try it by any chance?

---

<div class="post-metadata">

**Author:** ![pawann](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@pawann](https://universal-blue.discourse.group/u/pawann)\
**Post date:** [April 9, 2024, 6:42am UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/7 "2024-04-09T06:42:44Z")

</div>

Hey guys, actually I made my own image using blue build yesterday, it was quite simple and I was also successful in making the changes I needed, rebasing to it was straightforward. I don’t think a user needs to have separate instructions.

This is my version of the image aka Pawzite 😅

> **[GitHub - pawann-2000/pawzite: This is a custom image based on bazzite from...](https://github.com/pawann-2000/pawzite)**
>
> This is a custom image based on bazzite from project Ublue, built using the bluebuild template. It contains isw for msi laptop fan control. - pawann-2000/pawzite

---

<div class="post-metadata">

**Author:** ![pawann](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@pawann](https://universal-blue.discourse.group/u/pawann)\
**Post date:** [April 10, 2024, 1:06pm UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/8 "2024-04-10T13:06:07Z")

</div>

Although I was successful in making my own image with packages installed, I think the instructions are still needed for some system level stuff - like custom kernel installation, custom de configuration ootb and other things

---

<div class="post-metadata">

**Author:** ![maxexcloo](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/maxexcloo/32/1752_2.png) [@maxexcloo](https://universal-blue.discourse.group/u/maxexcloo)\
**Post date:** [June 11, 2024, 1:35pm UTC](https://universal-blue.discourse.group/t/fork-your-own-image/43/9 "2024-06-11T13:35:16Z")

</div>

Between the following I take it blue-build is the way forward?

> **[GitHub - ublue-os/image-template: Build your own custom Universal Blue Image!](https://github.com/ublue-os/image-template)**
>
> Build your own custom Universal Blue Image! Contribute to ublue-os/image-template development by creating an account on GitHub.

> **[GitHub - ublue-os/image-template: Build your own custom Universal Blue Image!](https://github.com/ublue-os/image-template)**
>
> Build your own custom Universal Blue Image! Contribute to ublue-os/image-template development by creating an account on GitHub.
