Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Battle For Wesnoth #237

Merged
merged 13 commits into from
Apr 19, 2024
Merged

Conversation

mattman107
Copy link

@mattman107 mattman107 commented Apr 6, 2024

Description

Added a yolk for The Battle For Wesnoth game. Needed some specific libraries in the main container to run. I have never used Github actions/workflows before so please let me know if I did something wrong with that.

For this PR: pelican-eggs/eggs#2863 (comment)

All Submissions:

  • Have you ensured there aren't other open Pull Requests for the same update or change?
  • Have you created a new branch for your changes and PR from that branch and not from your master branch?

New Image Submissions:

  1. Have you added your image to the Github workflows?
  2. Have you updated the README list to contain your new image?

ENV DEBIAN_FRONTEND noninteractive

## add container user
RUN useradd -m -d /home/container -s /bin/bash container
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since you are need a user, is this not the correct way?

## Setup user and working directory
RUN         useradd -m -d /home/container -s /bin/bash container
USER        container
ENV         USER=container HOME=/home/container
WORKDIR     /home/container

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I am new to making containers. So
USER container
this sets what user is logged into right?

And
ENV USER=container HOME=/home/container
These are variables required for pterodactyl to do its thing?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I am new to making containers. So USER container this sets what user is logged into right?

And ENV USER=container HOME=/home/container These are variables required for pterodactyl to do its thing?

no, you only set the user for the container and the working dir.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. That looking better?

Copy link

@gOOvER gOOvER Apr 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. That looking better?

you deleted the wrong line :)

@@ -2,10 +2,11 @@ FROM --platform=$TARGETOS/$TARGETARCH ubuntu:22.04

LABEL author="Michael Parker" maintainer="parker@pterodactyl.io"

ENV DEBIAN_FRONTEND noninteractive
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

leaves this, but with:

ARG DEBIAN_FRONTEND noninteractive

Copy link
Author

@mattman107 mattman107 Apr 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I did this but did I need both lines or just the one you have stated?

ENV DEBIAN_FRONTEND noninteractive
ARG DEBIAN_FRONTEND noninteractive

or just

ARG DEBIAN_FRONTEND noninteractive

README.md Outdated Show resolved Hide resolved
@mattman107 mattman107 closed this Apr 6, 2024
@mattman107 mattman107 deleted the TheBattleOfWesnoth branch April 6, 2024 17:09
@mattman107 mattman107 restored the TheBattleOfWesnoth branch April 6, 2024 17:09
@mattman107 mattman107 reopened this Apr 6, 2024
@mattman107 mattman107 changed the title The Battle of Wesnoth The Battle For Wesnoth Apr 6, 2024
@mattman107
Copy link
Author

Forgive me for my ignorance, but I noticed in the games.yml file that it says

runs-on: ubuntu-latest

So I assumed that I had to make the Dockerfile using ubuntu like this

FROM --platform=$TARGETOS/$TARGETARCH ubuntu:22.04

Do I have to use ubuntu or could I use a debian base instead?

@QuintenQVD0
Copy link
Collaborator

Forgive me for my ignorance, but I noticed in the games.yml file that it says

runs-on: ubuntu-latest

So I assumed that I had to make the Dockerfile using ubuntu like this

FROM --platform=$TARGETOS/$TARGETARCH ubuntu:22.04

Do I have to use ubuntu or could I use a debian base instead?

Its just what the workflow runs on. But keep in mind that we moved to debian 12 if possible.

@mattman107
Copy link
Author

Got it. I will change it to debian then.

@mattman107
Copy link
Author

mattman107 commented Apr 10, 2024

So I wasn't able to get the github actions working, but I started doing testing manually building the container and uploading it to dockerhub. I have successfully gotten the egg to work properly using the container now in this PR.

@mattman107
Copy link
Author

Are any PRs on hold until the whole Pelican restructure situation is figured out?

I have been a bit out of the loop, but really excited to get a chance to it try out.

@QuintenQVD0
Copy link
Collaborator

Are any PRs on hold until the whole Pelican restructure situation is figured out?

I have been a bit out of the loop, but really excited to get a chance to it try out.

This repo will become soon read only. All pr must be moved to their individual repo's

@mattman107
Copy link
Author

Are any PRs on hold until the whole Pelican restructure situation is figured out?
I have been a bit out of the loop, but really excited to get a chance to it try out.

This repo will become soon read only. All pr must be moved to their individual repo's

Wait so there will no longer be a single unified yolk repository?

In this case where the game requires its own custom docker image to run, what repo would I be making a PR for?

@QuintenQVD0
Copy link
Collaborator

Are any PRs on hold until the whole Pelican restructure situation is figured out?
I have been a bit out of the loop, but really excited to get a chance to it try out.

This repo will become soon read only. All pr must be moved to their individual repo's

Wait so there will no longer be a single unified yolk repository?

In this case where the game requires its own custom docker image to run, what repo would I be making a PR for?

Yolks will stay 1 single yolks repo.

@mattman107
Copy link
Author

mattman107 commented Apr 18, 2024

Are any PRs on hold until the whole Pelican restructure situation is figured out?
I have been a bit out of the loop, but really excited to get a chance to it try out.

This repo will become soon read only. All pr must be moved to their individual repo's

Wait so there will no longer be a single unified yolk repository?
In this case where the game requires its own custom docker image to run, what repo would I be making a PR for?

Yolks will stay 1 single yolks repo.

Alright so this PR for the yolk is still in the right place, but the original PR draft for the egg should be moved to the games repo. Am I understanding that correct?

@QuintenQVD0
Copy link
Collaborator

Are any PRs on hold until the whole Pelican restructure situation is figured out?
I have been a bit out of the loop, but really excited to get a chance to it try out.

This repo will become soon read only. All pr must be moved to their individual repo's

Wait so there will no longer be a single unified yolk repository?
In this case where the game requires its own custom docker image to run, what repo would I be making a PR for?

Yolks will stay 1 single yolks repo.

Alright so this PR for the yolk is still in the right place, but the original PR draft for the egg should be moved to the games repo. Am I understanding that correct?

yes you are.

Copy link
Collaborator

@QuintenQVD0 QuintenQVD0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, lets start with this

@QuintenQVD0 QuintenQVD0 merged commit 3798aba into pelican-eggs:master Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants