From 9683d747ccb0251ee87c1298762254e884b8d550 Mon Sep 17 00:00:00 2001
From: he3als <65787561+he3als@users.noreply.github.com>
Date: Sun, 25 Aug 2024 02:19:59 +0100
Subject: [PATCH] fix(docker): alpine dependencies

---
 Dockerfile | 3 ++-
 README.md  | 2 ++
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/Dockerfile b/Dockerfile
index e11cc5804..6fb10c37a 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -3,7 +3,8 @@
 FROM --platform=$TARGETOS/$TARGETARCH alpine:latest
 WORKDIR /app
 COPY . ./
-RUN curl -fsSL https://bun.sh/install | bash && exec bash \
+RUN apk add --no-cache --update curl \
+    && curl -fsSL https://bun.sh/install | sh && exec sh \
     && bun i --frozen-lockfile \
     && bun ship
 
diff --git a/README.md b/README.md
index a5a3bacd1..ce14c29e3 100755
--- a/README.md
+++ b/README.md
@@ -136,8 +136,10 @@ Using [Vagrant](https://www.vagrantup.com) on Linux is incredibly simple. Verify
 1. Clone the Pyrodactyl panel repository
 2. Run `bun i` to install all required packages
 3. Run `bun ship` to build Pyrodactyl. This will cache the results of the build and upload sourcemaps to Sentry. Subsequent builds without code changes will finish in milliseconds.
+
 > [!IMPORTANT]
 > In order for `vagrant up` to work, your files must be in the `/var/www/pterodactyl` directory unless manually changed in the `Vagrantfile`!
+
 4. Run `vagrant up`. This will setup wings and the necessary services in order to run Pyrodactyl's databases, services, and app. This process could take up to 15 minutes.
 5. Once you receive a message that says "Pyrodactyl is now up and running at localhost:3000", visit that URL in your browser and login with the default credentials provided in your console. **It's important that you use localhost to connect to Pyrodactyl! If you use 127.0.0.1, you will run into CORS issues and other issues that will not be fixed.**