Blueprint in Ptero Docker
So as the title says, I'm trying to get Blueprint installed on Pterodactyl running inside a container.
I'm using Doacola's Dockerfile and have created my custom image and am using that in my compose file just stuck on the next steps? Do i just continue the install as normal? Or do i do it while attacthed to the running container and wget the files there unzip and run the .sh? Just unsure as what the next steps are with this.
Any help would be greatly appreciated, thank you.
5 Replies
@Doacola Sorry but you are the tech support of this matter #IHateDocker
oh no doacola is becoming docker tech support
(if you'd prefer to not have people ping you for this stuff just lmk)
Well as I have said I haven't tried the docker on last few versions as been busy irl but in general yes you should be able to do the install normally as long the required packages etc are installed on the custom docker image so it's up to the user themselves to verify whether latest version works and potentially modify it with possible fixed
Also this might sound rude but I have also warned that if one wants to dabble with docker and blueprint they should have decent knowledge of docker works under the hood in the first place as the install process also requires certain changes (potentially still) on the blueprint.sh file itself in regards of path etc as docker deviates from baseline ptero paths and whatnot. Hence why I generally don't recommend blueprint with docker(despite the lovely rollback/reset features) unless one has the required base knowledge and is willing to figure things out on the go when needed 😄
Ah so you actually have to edit the .sh file itself not as easy as just creating your own Dockerfile and running it inside the container
Could you just not get the panel files outside a container, put the blueprint files in, run it so it installs and then once it’s all installed then create a new docker image with blueprint already preinstalled to pterodactyl?
The thing is that as long as Purple doesn't publicly state that docker is fully supported the expectation is that you are on your own. Surely one could try maintain their own image repo that installs new BP version on fresh ptero image but there are no guarantees as the docker setup in the past has been pain in the ass.(I am off by several versions now so I don't know if same issues still persist or have new ones appeared as stated before)
One of the ways that has been mentioned in the past to make BP more docker compatible would more or less need BP to transition into same way other theme creators etc have gone: modify their changes directly into ptero files and offer the whole package combo but that's another can of worms itself