Go to file

Red-Thirten 06ca1edce7 Added Arma 3 image files

These files originate from https://github.com/parkervcp/images/tree/game/arma3 which is currently hosted at quay.io/parkervcp/pterodactyl-images:game_arma3
However, the entire image has been mainly rewritten in this update, which includes the following changes:
- Code styling / nomenclature has been normalized across the entire file.
- A robust RunSteamCMD function has been added to run SteamCMD with advanced error handling and reporting. Works for both the server and mods, and is configurable with the STEAMCMD_ATTEMPTS environment variable to specify how many times it should retry a download after a recoverable error (like large Workshop mod downloads timing out).
- Added support for a MOD_FILE environment variable, to specify an exported Arma 3 modlist HTML file for import into the server (for downloads and runtime). These mods are combined with any mods listed in MODIFICATIONS.
- A more robust and automatic way of downloading/updating mods is now included with the UPDATE_SERVER function. All mods to be used during runtime are checked for updates by comparing local file's creation dates against the mod's Workshop page last update. This allows for fast and reliable mod updates compared to the old manual system, and allows users to comfortably leave the update server function on all the time if they'd like.
- Added a RemoveDuplicates function to prevent a user from accidentally loading a mod twice.
- Checks for missing, trailing semicolons in manual mod lists due to human error.
- Mod update information echos are less cryptic and now use the mod's human-readable name, as well as printing the date they last updated.
- Made the server binary check error messages less cryptic and provided solution recommendations.
- Added a CLEAR_CACHE env. var. function to delete headless client profiles on startup to help with potential issues they cause.
- Un-hardcoded the basic.cfg URL and replaced with env. var.
- Added HC_HIDE env. var. to prevent headless client console spam.
- Added VALIDATE_SERVER env. var. to manually validate, because the new automatic update function skips validation to speed it up.
- Added CDLC env. var. for easy download of Creator DLCs incase the user doesn't know how to use SteamCMD beta branches.

2021-07-12 17:01:41 -07:00

.github/workflows

Add setup-qemu-action for arm64 (#8 )

2021-07-09 13:03:10 -06:00

games

Added Arma 3 image files

2021-07-12 17:01:41 -07:00

Actually correct command running...

2021-05-29 10:52:55 -07:00

installers

Change source to debian

2021-05-29 21:16:28 -04:00

java

Use only 8, 11, 16 (and OpenJ9 variants)

2021-07-04 14:56:00 -07:00

nodejs

Actually correct command running...

2021-05-29 10:52:55 -07:00

oses

Build the new images

2021-06-21 20:13:08 -04: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

Update README.md

2021-07-12 16:50:32 -07:00

README.md

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
arma3
- ghcr.io/pterodactyl/games:arma3
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
- java7
  - ghcr.io/pterodactyl/yolks:java_7
- java8
  - ghcr.io/pterodactyl/yolks:java_8
- java9
  - ghcr.io/pterodactyl/yolks:java_9
- java11
  - ghcr.io/pterodactyl/yolks:java_11
- java14
  - ghcr.io/pterodactyl/yolks:java_14
- java16
  - ghcr.io/pterodactyl/yolks:java_16
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

alpine-install
- ghcr.io/pterodactyl/installers:alpine
source-install
- ghcr.io/pterodactyl/installers:source