Pterodactyl on Docker compose installing blueprint extension error.
Im trying to install a theme on my ptero panel using blueprint, specifically the nebula theme. and when running
blueprint -install nebula I have an error 62 Replies
Context : docker, but not the blueprint docker image
it is isnt it?
??
like
what docker image do you use
ohh
oh so it is the blueprint docker image
okay
you made the alias ?
yep
followed the example
??
i did that but the path to my extension folder is slightly different
what is it
/home/george/mypterodactyl/extensions/
so you changed it ?
welp idk i never used blueprint docker i'm letting @Loki or @Emma HHelp you
in the docker-compose file?
ahahaha thanks anyway mate
I was told extensions would always end in .blueprint. The image wasn't made to handle zip files.
Try extracting the zip file and putting the contents in extensions. I'm assuming every file in the zip will have blueprint somewhere in the name.
There is no zip file ahahahah
Idk why it’s saying that
The extension in the folder is nebula.blueprint
When I run the command to install the extension it starts talking about a zip file that I don’t think exists 😭
@Emma What actually happens when the .blueprint file is being installed?
At this point in the container, the nebula.blueprint file is inside of /app and blueprint -install is run on it. The /app directory is persistent.
I did test with the recolor extension, but maybe more complex extensions do other things I haven't accounted for.
@George' Can you show the contents of your extensions folder btw? And run
docker compose exec panel ls -a /blueprint_extensions && echo "\n" && ls -a /app and post the results here?extensions use zip compression and are unarchived upon installation. they are all exported the same way, so if one works, the rest generally should as well
So blueprint downloads the .zip file to the current directory? Still /app? Then it just unzips?
Would any of the files have blueprint in the name?
Currently, the sync puts any files in extensions that have
.blueprint anywhere in the name into /app, as well as deletes any files that have that in the name that are no longer in extensions (with the exception of /app/.blueprint).
The reason it's *.blueprint* for the sync is because recolor put a second file in extensions with .blueprint in the name that has :ZoneIdentifier after the .blueprint; I assumed that would need to go in app too. But if there are going to be more files in /app with .blueprint somewhere in the name, I need to modify the logic.Yep give me two minutes
@Loki
Put quotes around it.
docker compose exec panel "ls -a /blueprint_extensions && echo "\n" && ls -a /app"If it doesn't like it starting with quotes,
docker compose exec panel sh -c 'ls -a /blueprint_extensions && echo "\n" && ls -a /app'Everything looks good... maybe it's an issue with the nebula extension. Have you tried it on a non-docker instance?
Nah I don’t have a non docker instance of pterodactyl
Try starting over. Take the stack down, delete the volume for it, then spin the stack back up and try again.
what am i deleting?
i dont thinking there is an app volume
docker volume lsohh
Did you wait a minute after starting the stack before you used blueprunt -install? The panel should still be doing a lot of setup at first. When
docker compose logs panel shows something about an http server, it's done.
Have you put any data on the panel yet? If not, start over.
okay its all set up
2024-04-22 05:12:24,567 CRIT Server 'unix_http_server' running without any HTTP authentication checking
ohhhh
its workingggg
okay now i need to remember how to make a user
@Loki how do i use the p:user:make command in docker compose?docker compose exec panel php artisan p:user:make
So nebula installed fine?well it installed fine
but the theme isnt like working
do i have to restart docker to get it working?
I'm not sure. The recolor theme worked instantly; I just refreshed the page.
looks very applied ahahahaha
Looks like Alpine by default doesn't have the right version of ln, 1 sec
@George'
blueprint -uninstall nebula and wait a minute for the new image to finish building.i dont have an alias for that command
Then
docker compose exec panel blueprint -uninstall nebula or set the alias.
Then docker compose down, wait until I let you know the new image finished building and pushing, and docker compose pull
@George' It's done building, you can pull it now
Let me know if the theme installs this timeidk what the command is them, maybe remove
Or you could delete the volume again
same thing again
Huh
-remove
was the command
just woke up haha if you need me to explain anything feel free to ping me
I just tested. -r definitely works now that I've install coreutils. Try taking the stack down again and pulling the image.
Once you've installed it successfully, check out this section.
here we gooooo
no errors so far
wooohoooooo
Nice.
When you're done configuring it, do this step. If it's already past 11:59PM for you, just run the script manually after you do that.
It does assume your compose file is in /srv/pterodactyl/docker-compose.yml, so if it's in another place, adjust the commands accordingly.
Yep sweet as I’ll do that now
Hello, sorry to bother you, i need some help. When i try to run the command "blueprint -install nebula", i get the error "stat /srv/pterodactyl/docker-compose.yml: no such file or directory". I tried to install pteroblueprint both with docker compose only and with portainer stacks. Where i can find the docker compose file i need to run the alias command?
CC @Loki - Could this be related to the repository rename?
Just if you need more information, the directory exists, only the docker compose file is missing for some reason. Sorry for the poor informations but i'm new to asking help. If you need some more infos, just ask me
Alright, might be good to open another forum post.
Done! Thank you
Solved by changing the alias to "echo 'alias blueprint="sudo docker exec mypanel-panel-1 blueprint"' >> ~/.zshrc"
Portainer uses different names. The tutorial was for the default compose file.
If you don't know where Portainer keeps the compose file, executing it directly from the container works fine too.
Ok, thank you very much. I didn't know that portainer uses different names. I tried to search for the compose file but i didn't found it. But now it's working this way 🙂