Docker images designed for use with Pterodactyl's Egg system.
Find a file
Alex 8afb47574c
ci: enable workflow dispatch
Allows manually triggering workflows to rebuild images. Works with push and schedule.
2021-09-23 01:35:21 +03:00
.github/workflows ci: enable workflow dispatch 2021-09-23 01:35:21 +03:00
games Update packages for Debian 11 (#16) 2021-08-22 20:53:09 +03:00
go Actually correct command running... 2021-05-29 10:52:55 -07:00
installers Update packages for Debian 11 (#15) 2021-08-22 20:53:28 +03:00
java Fixes for arm64 and Debian Bullseye (#18) 2021-09-22 16:01:08 +03:00
nodejs Actually correct command running... 2021-05-29 10:52:55 -07:00
oses Fixes for arm64 and Debian Bullseye (#18) 2021-09-22 16:01:08 +03:00
python Actually correct command running... 2021-05-29 10:52:55 -07:00
.editorconfig Attempt to fix timezone problems with images 2020-10-25 11:23:45 -06:00
.gitignore fork over the work from @matthewpi 2021-05-15 11:26:03 -07:00
LICENSE.md Initial Commit 2020-07-19 11:26:09 -06:00
README.md Merge branch 'master' into update/readme 2021-08-03 15:54:31 -04:00

Yolks

A curated collection of core images that can be used with Pterodactyl's Egg system. Each image is rebuilt periodically to ensure dependencies are always up-to-date.

Images are hosted on ghcr.io and exist under the games, installers, and yolks spaces. The following logic is used when determining which space an image will live under:

  • games — anything within the games folder in the repository. These are images built for running a specific game or type of game.
  • installers — anything living within the installers directory. These images are used by install scripts for different Eggs within Pterodactyl, not for actually running a game server. These images are only designed to reduce installation time and network usage by pre-installing common installation dependencies such as curl and wget.
  • yolks — these are more generic images that allow different types of games or scripts to run. They're generally just a specific version of software and allow different Eggs within Pterodactyl to switch out the underlying implementation. An example of this would be something like Java or Python which are used for running bots, Minecraft servers, etc.

All of these images are available for linux/amd64 and linux/arm64 versions, unless otherwise specified, to use these images on an arm system, no modification to them or the tag is needed, they should just work.

Contributing

When adding a new version to an existing image, such as java v42, you'd add it within a child folder of java, so java/42/Dockerfile for example. Please also update the correct .github/workflows file to ensure that this new version is tagged correctly.

Available Images

  • alpine
    • ghcr.io/pterodactyl/yolks:alpine
  • debian
    • ghcr.io/pterodactyl/yolks:debian
  • fivem
    • ghcr.io/pterodactyl/games:fivem
  • golang
    • go1.14
      • ghcr.io/pterodactyl/yolks:go_1.14
    • go1.15
      • ghcr.io/pterodactyl/yolks:go_1.15
    • go1.16
      • ghcr.io/pterodactyl/yolks:go_1.16
  • java
  • nodejs
    • node12
      • ghcr.io/pterodactyl/yolks:nodejs_12
    • node14
      • ghcr.io/pterodactyl/yolks:nodejs_14
    • node15
      • ghcr.io/pterodactyl/yolks:nodejs_15
    • node16
      • ghcr.io/pterodactyl/yolks:nodejs_16
  • python
    • python3.7
      • ghcr.io/pterodactyl/yolks:python_3.7
    • python3.8
      • ghcr.io/pterodactyl/yolks:python_3.8
    • python3.9
      • ghcr.io/pterodactyl/yolks:python_3.9

Installation Images