Go to file

Red-Thirten e750a642c9 Arma 3 Image Cleanup & Refurbishment

Files:
- Remove dependency of having `libnss_wrapper.so` libraries directly in the image. Instead, use the libraries provided with their respective packages. This fixes the current 32-bit version being broken and ensures the libraries stay up to date with their respective packages.
- Slight change to passwd.template to accommodate variable name change.

Dockerfile:
- Change the base image to Debian, which from testing appears to run cleaner and faster for Arma. It also should yield a smaller image.
- Fix depreciated `ENV` call format.
- Removed un-needed packages.
- Added iproute2 package.
- Consolidated the NSS Wrapper setup to a commented group of lines to make understanding it's purpose and setup more clear.
- Added shell flag to `useradd` command.

Entrypoint:
- General cleanup.
- Changed `LD_PRELOAD`s to point to package-provided library file locations.

2022-05-22 17:35:03 -07:00

.github

fix alphabetical orde

2022-05-02 17:54:08 +02:00

bot

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

cassandra

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

dotnet

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

erlang

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

games

Arma 3 Image Cleanup & Refurbishment

2022-05-22 17:35:03 -07:00

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

installers

feat: add unzip zip tar jq

2021-11-18 21:38:10 +02:00

java

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

mariadb

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

mongodb

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

mono

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

nodejs

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

oses

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

postgres

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

python

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

redis

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

rust

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

voice/teaspeak

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03:00

wine

fix: invalid INTERNAL_IP environment value

2022-04-24 18:10:20 +03: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

fix alphabetical orde

2022-05-02 17:54:08 +02: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.