diff --git a/Dockerfile b/Dockerfile
index 7e577a5..a065a1e 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -14,11 +14,11 @@ RUN nvm install
 RUN nvm use
 
 COPY package*.json ./
-RUN npm ci --omit=dev
+RUN npm ci --omit=dev --ignore-scripts
 
 COPY . .
 ENV NEXT_TELEMETRY_DISABLED=1
 RUN npm run build
 
 EXPOSE 3000
-CMD ["/root/.nvm/nvm-exec", "npm", "run", "start"]
\ No newline at end of file
+CMD ["/root/.nvm/nvm-exec", "npm", "run", "start"]
diff --git a/README.md b/README.md
index 675312f..a8ff281 100644
--- a/README.md
+++ b/README.md
@@ -53,6 +53,6 @@ LEMMY_BACKEND=https://<your lemmy api> LEMMY_UI_NEXT_PUBLIC_URL=https://<url whe
 
 At this point, you will have lemmy-ui-next listening on 0.0.0.0:3000, and you can point your nginx or any other reverse proxy at it. You can improve performance at least a little by pointing lemmy-ui-next directly at your Lemmy backend process. For examplem if running on the same host, you can use something like `LEMMY_BACKEND=https://localhost:8536`.
 
-*Sample systemd service file will be coming soon. Alternatively, a sample Dockerfile will also be provided. It's on the to-do list 😅.*
+*Sample systemd service file will be coming soon. It's on the to-do list 😅. Alternatively, a sample Dockerfile is provided.*