Closed christianuhlmann closed 5 years ago
Hi,
Yes, I've notice that, I'll look for it asap. It work on a local build but not on a docker hub service. That's annoying. I've tag a 5.30 version in sync with their 5.30, we are still ahead of the official version.
Would there be a workaround available to get plugins into a running container of the latest image?
Don't see one for now, I need to make the links in the build image and they seems to not be copied by the COPY
command when I build the running image. But I need to check what's going on in the file system, the issue is caused by COPY
or yarn link
command or a combination of both.
For now daily build are stopped and latest
is bind on the last tagged version I build.
Same here. It seems that yarn linking has strange paths in the final image:
/home/node/xen-orchestra/packages/xo-server/node_modules: xo-server-auth-github -> ../../../../../../usr/local/share/.config/yarn/link/xo-server-auth-github xo-server-auth-google -> ../../../../../../usr/local/share/.config/yarn/link/xo-server-auth-google xo-server-auth-ldap -> ../../../../../../usr/local/share/.config/yarn/link/xo-server-auth-ldap
Path /usr/local/share/.config does not even exist and node_modules for each plugin is empty - so either plugins are not build or not copied. Hope this helps.
Besides that current link-script might not even work at all because of typo - see my pull request. https://github.com/Ezka77/xen-orchestra-ce/pull/11
But that does not fix the underlying problem of modules not linked.
Update: the plugins are there - just the paths mentioned above are wrong. So @Slugger for me the following temporary workaround brings up the plugins for a already build xo container:
docker ps
- example: 0123456789ab sudo docker exec -ti 0123456789ab bash
cd /home/node/xen-orchestra/packages/xo-server/node_modules
ln -f -s ../../xo-server-auth-ldap
sudo docker restart 0123456789ab
Every time you recreate the container via build you have to recreate the links. Hope the container image gets fixes soon.
Confirming that this workaround works for me.
Great !
I've made some updates: the 5.32
docker tag is locally build with a new link_plugins.sh
, I've start a build on docker-hub for the latest
tag, and the plugins are loaded in both cases.
Thanks @mhoffmann75 for checking the file system and testing if a simple ln
do the trick =)
hi, in the latest version the plugins are missing. upto tag 5.30 all plugins are available regards christian