Pterodactyl in docker & Blueprint
Hey, So we had pterodactyl installed the standard way and now we are migrating to pterodactyl installed in docker, so because we had blueprint on the panel installed the standard way i cant install the blueprint now through the blueprint.sh since that says [WARNING] This command only works if you have yet to install Blueprint. Run 'blueprint (cmd) [arg]' instead. So we cant install it through that way, then i tried it through blueprint -rerun-install but that made this error with yarn.
ERROR in resources/scripts/components/server/files/UploadButton.tsx:88:78
TS2345: Argument of type 'AxiosProgressEvent' is not assignable to parameter of type 'ProgressEvent<EventTarget>'.
Type 'AxiosProgressEvent' is missing the following properties from type 'ProgressEvent<EventTarget>': lengthComputable, target, bubbles, cancelBubble, and 19 more.
86 | headers: { 'Content-Type': 'multipart/form-data' },
87 | params: { directory },
88 | onUploadProgress: (data) => onUploadProgress(data, file.name),| ^^^^ 89 | } 90 | ) 91 | .then(() => timeouts.value.push(setTimeout(() => removeFileUpload(file.name), 500))) error Command failed with exit code 2. After i did this i moved all the files from directory where i run the -rerun install (thats other directory that /var/www/pterodactyl)to the docker container and the panel doesnt even load. Then i tried moving the old files (from /var/www/pterodactyl) to the docker container but it went with error 404 The requested resource was not found. when trying to access admin. Is there a way to make it working with pterodactyl in docker? Thanks
11 Replies
@Doacola Sorry for mentioning you. I can't really explain much on how it works as I've not done a bunch of crap with Docker just yet.
Let me know if you'd prefer not getting pinged for stuff like this.
Hi, I have sent my variant of the Dockerfile in general once or twice now for starters that make the way so blueprint should work like expected via CLI. For the error of running there might be time where you need to run the
blueprint.sh file directly from the directory and not the one "thrown in usr/bin" side of things. For the yarn errors I can't help much because I've never had that issue myself so it could be too new/old nodejs version or package version which is more in the area of ptero itself if nodejs side kicks rocks.^- on an unrelated note,
-debug [amount-of-lines] will be on blueprint on version alpha-NLM (which now all silenced logs are sent to)Nice
Best to do when attempting to fix yarn errors is to just rm the node_modules folder and run the
yarn command after. (Fixes most weird yarn errors.)That is one but it could be that incompatible node version is installed or somehow installed too fresh axios npm during yarn install.
The way I lately have started to do things is if ptero or bp "bricks" I remove the volume mount(persistent storage), either delete it or start a new volume mount so the container becomes to state of "as it never was modified" with exception of keeping the env file transferred and run the bp install "again" on "fresh setup" and if I have any custom stuff for ptero directly, I am mounting those as "read-only" from outside the overall persistent storage so in case of bricking I have my changes safe that can be put back and worry about other potential extensions like blueprint
also I need to mention about that
/var/www/pterodactyl part in rejsiks message: when you use docker you want to modify the path to be /app(Ptero devs still use this layout for docker instead of the one in their guides etc that only apply if you do everything from scratch on a server not to mention it seems like they don't give a damn about docker and prob wish the image would die). So whenever you see that www path remember to flip your docker brain to see it as "/app". Having BP with ptero will not be easy if doing it yourself with docker but it is doable... I am not the only one that has done it but it's absolutely PITA(I haven't checked for a bit if it still needs the yanky file modification for upgrade process on BP side 😄 )Thanks for the info,would you be open to sending you dockerfile?
@Doacola
^- pinned it in general
Got it working, thanks
So i've created a new dockerfile and changed it in my docker compose, do i just go about installing BP as normal now or?