libzip | C library for reading , creating , and modifying zip archives | Compression library

In general, this is not possible, but there are workarounds (I do not recommend them for production). The superuser UID is always 0, this is written in the kernel code. It is not possible to automatically change the ownership of non-root files. In this case, when developing, you can use these methods:

If superuser rights are not required: You can create users dynamically, then docker-compose.yml:

It turns out the problem was the encoding of my source file itself. It was ANSI - So I converted it to UTF8 and it solved the issue.

What I still don't understand is why libzip can't zip_name_locate() a name from an input c-string that is exactly the same as the input c-string used in zip_file_add() (whatever the source file encoding might be). "Lost in translation" perhaps ?

(Special thanks to Thomas Klausner for helping me find the issue).

PHP 8.0.15 and 8.1.2 has a bug which is breaks compile sockets extension.

You have a two options:

1. Skip this versions.
2. Apply a workaround to bypass bug and build sockets extenstension.

Source:

• Issue at origin PHP source repository
• Issue at official PHP Dokcer image source repository

I would go with neither of the above; instead, run composer install locally and copy the resulting vendor directory as part of your application.

Fetching dependencies is fundamentally part of building an application, not part of running it, so Composer shouldn't even be installed on a production host or container. If you were writing a C application which needed to be compiled with gcc, you would run that as an earlier step, and then copy the binary into the container; composer install can be treated the same way.

So for instance, you might have a build script (to run manually, or in a CI server like Jenkins, Github Actions, Azure DevOps, etc) that went through the following steps:

1. Clone the repo from a git repository
2. Check out the latest tag
3. Run composer install
4. Run a script to minify the client-side JS
5. Run docker-composer, copying the source code, minified JS, and vendor directory

The software inside the Docker container therefore only needs to be able to run the application, not build it.

I finally found a way to make it work. Here's what I did

Expose port 3000 in my app container:

Is it possible to not generate build systems for everything whats under lib/ and instead compile and link the library directly into the Engine project?

This sounds like an XY problem. What do you really want to do?

1. Are you trying to avoid CMake spending time configuring those projects? If they're really optional, then add option()s to disable them.
2. Are you spending a lot of time rebuilding everything when you only want some parts? Let me point you to the cmake --build ... --config --target Game command. That will build only what is needed for target Game.
3. Something else?

But this question of not "generat[ing] build systems" is ill-formed. CMake is a build system generator. How do you make a C++ compiler not compile C++?

Please have a look at the documentation of Composer scripts. It explains pretty obvious:

post-install-cmd: occurs after the install command has been executed with a lock file present.

If you are using composer install with a lock file not present (as indicated from the console output), this event is not fired.

Because you are using ";" after the supervisord command, the command waits for supervisord to finish and after that cron will run. You can make it like: