Removal of Authentik Script from Community-Scripts

[MickLesk]

Hello all,

After numerous recurring issues, we have decided to remove the Authentik script from our collection.

Despite several attempts to stabilize the installation and update process, Authentik has proven to be increasingly unmaintainable in our ecosystem. Frequent breaking changes, problematic builds, and inconsistent behavior have led to dozens of bug reports and support threads over the last few months.

More critically, the latest versions of Authentik now require at least 14 GB of RAM and 8 CPU cores to build, which we believe is completely disproportionate for a standalone authentication provider.

⚠️ If the Authentik team eventually decides to provide a maintainable packaging method (such as a .deb package, a clean npm/uv setup, or a prebuilt binary like ActualBudget), we are open to re-evaluating this decision in the future.

Until then, the combination of resource requirements, maintenance complexity, and error frequency makes continued support untenable.

---

🧾 References – A Selection of Related Issues

• #4867: Remove Authentik script – merged
• #4851: npm run build-bundled fails
• #4591: /dev/fd/63: SPINNER_PID: unbound variable
• #4364: RAM increased to 10 GB – merged
• #4195: Broken update (duplicate)
• #4156: authentik install error – 24 comments
• #3408: Go build failed – not script-related
• #3391: PEP517 build error – not script-related
• #2879: "Cannot update Authentik"
• #2843: Install hangs on Python 3
• #2327: Embedded Outpost upgrade fix – merged
• #2020: Remove deprecated GO footer – merged
• ...and many more.

---

Thank you to everyone who contributed bug reports, PRs, and feedback. Your efforts have been instrumental in helping us make this decision.

— Community-Scripts Maintainers

[alienatedsec]

Anyone interested in using Authentik in Proxmox could install the Docker LXC, and run the following commands:

apt update
apt install docker-compose

Follow the rest from https://docs.goauthentik.io/docs/install-config/install/docker-compose

Updating this way is also much easier to follow:

Download the docker-compose.yml file using either

wget -O docker-compose.yml https://goauthentik.io/docker-compose.yml

or

curl -O https://goauthentik.io/docker-compose.yml

Then execute the following

docker compose down
docker compose pull
docker compose up -d

[Patrick010]

That is exactly what we don't want 🤣

[HearthCore]

Welcome to IT, where when it don't work like exactly like you want, you either make it seem like it does or treat it as such through other means.

Nail? Hammer. Screw? Hammer HARDER!

Namingly, want it to automatically do it's thing when using a global update script? Now's when frustration and laziness battles and then.. well.. you can always pct exec VMID cd /authentik && wget .. && docker compose pull && docker compose down && docker compose up -d, then pipe the result with error code and indication where it would produce the error with the original script.

then you .. well.. git clone the repo, adjust those parameters and maybe provide a global config.yml for those advanced settings one can use as an "Update docker compose projects on LXC host"-script for the Repo!

[Popcorncandy09]

For anyone who is interested i have managed to put together a standalone .sh file that can be run locally and seems to update the LXC fine. Here

This was made due to devs pulling the Authentik script.

[boxedge]

[INFO] Docusaurus version: 3.7.0
Node version: v22.16.0
ERROR: "build:docusaurus" exited with 1.
root@authentik:/home#

[Popcorncandy09]

Open the main update script in the nano editor:

Find this specific section of code:

echo -e ":: Building Authentik frontend..."
cd /opt/authentik/website
npm install > /dev/null
npm run build-bundled > /dev/null
cd /opt/authentik/web
npm install > /dev/null
npm run build > /dev/null
echo "Frontend built successfully."

You need to remove the > /dev/null from the ends of the four npm command lines. This will stop the script from hiding the output. Make the section look exactly like this:

echo -e ":: Building Authentik frontend..."
cd /opt/authentik/website
npm install
npm run build-bundled
cd /opt/authentik/web
npm install
npm run build
echo "Frontend built successfully."
Press Ctrl+X, then Y, and Enter to save the changes.
Step 2: Re-run the Script and Capture the Full Log

Now, run the update script again

The script will now produce a very long and detailed output, especially during the Building Authentik frontend... step. Please let it run until it fails again.

[EcN000]

Where does it say on Authentik docs 14gb and 8 cores? The docker compose says 2gb and 2 cores? Sorry I just started looking into Authentik.

[MickLesk]

Without this, the LXC dont run. Then use docker, End.

[alienatedsec]

Where does it say on Authentik docs 14gb and 8 cores?

@EcN000
These are requirements to build from the source and not to run.

[jsapede]

switched to pocketid and oauth2-proxy way easier and lightweight than authentik