Describe the bug
When trying to build a byte code repository in docker, hhvm 4.168 fails with a set_mempolicy: Operation not permitted
Standalone code, or other way to reproduce the problem
<<__EntryPoint>>
function main(): void {}
hhvm.repo.authoritative=true
hhvm.repo.path=./hhvm.hhbc
hhvm.server.allow_run_as_root=true
Steps to reproduce the behavior:
- Create an empty Hack project in an hhvm/hhvm docker container
- Add an empty hhconfig file.
- Put an empty entry point, as shown above in src/main.hack
- Put the INI file shown above in repo-auth.ini
- Create a repo using
hhvm --hphp --input-dir $(pwd) --output-dir .
- When running under hhvm/hhvm@4.167-latest, observe a successful creation of hhvm.hhbc in the project directory.
- Run the server using
hhvm -m server --no-config -c repo-auth.ini
- Curl (with option verbose flag) localhost from within the container. Observe an HTTP 200 without content.
Expected behavior
As described in steps to reproduce
Actual behavior
Step 5. fails with the following error:
...
Extern worker error while indexing: Execution of `hphpc-index` failed: exited with status 1
stderr:
set_mempolicy: Operation not permitted
...
Environment
Host system Ubuntu 22.04.
hhvm/hhvm on dockerhub
4.168.0, as provided in the docker container
Additional context
I did already change the commands to be compatible with the removed cli flags from hhvm 4.167.0.
Describe the bug
When trying to build a byte code repository in docker, hhvm 4.168 fails with a
set_mempolicy: Operation not permittedStandalone code, or other way to reproduce the problem
Steps to reproduce the behavior:
hhvm --hphp --input-dir $(pwd) --output-dir .hhvm -m server --no-config -c repo-auth.iniExpected behavior
As described in steps to reproduce
Actual behavior
Step 5. fails with the following error:
Environment
Additional context
I did already change the commands to be compatible with the removed cli flags from hhvm 4.167.0.