Xiwen Cheng

Also ran into this issue. I fixed it by changing the environment variables in `docker-compose.yaml` to: ```yaml environment: - PGID=0 - PUID=0 ``` From the default of `1000`. The plugin...

@jmeeske interesting... thanks for sharing the finding! If that's the case then i suspect there's potentially an issue with kernel compatibility of binfmt. https://askubuntu.com/questions/20246/running-a-mono-program-without-typing-in-mono-foo-exe A workaround would be to call...

@ppoetsma we use this buildpack at a customer I know for sure are on mendix 10.x . However last week another customer reported similar issue as above for mendix 10.12....

> 2024-08-08T11:23:11.3525199Z #16 24.83 Cannot open assembly '/opt/mendix/build/.local/mxbuild/modeler/mxbuild.exe': No such file or directory. This was a different issue and upgrading to docker-mendix-buildpack v5.0.5 fixes it.

Hi, Can you provide more details? Like error message. The message above doesnt say much other than "it does not work". Xiwen

Ah yeah, mendix-rootfs:builder cannot be pulled because it does not exist. Follow the instructions at https://github.com/mendix/docker-mendix-buildpack/blob/master/upgrading-from-v4.md to fix.

@devatnl can you please attach the affected jars here as attachments? That would speed up the bugfix.

The reason why this is being detected incorrectly is: ``` 06:55:09.608 getJarProps ▶ DEBU 00a Parsed properties from MANIFEST: {2.13.4.2 2013004002 resources/jars/jackson-databind-2.13.4.2.jar jackson-databind-2.13.4.2.jar com.fasterxml.jackson.core.jackson-databind jackson-databind FasterXML http://www.apache.org/licenses/LICENSE-2.0.txt} 06:55:09.608 listAllJars ▶...

Hi Zeeshan, feel free to implement this. Didnt get around to do this yet.

There is one catch (challenge): how to deal with transitive dependencies. Not all jars will have a direct dependency from a java file. How do we know a jar depends...