phpDocumentor / phpDocumentor/phpDocumentor

Phar is modified on a run

Open
#3,582 26 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
4.3k
Forks
648
Avg merge
28m
Merged PRs (30d)
13

Description

          I'm still getting an error with phive on Docker:
Notice: require(): zlib: data error in /tools/.phive/phars/phpdocumentor-3.4.1.phar on line 11

Warning: require(phar://phpdocumentor.phar/bin/phpdoc): Failed to open stream: phar error: internal corruption of phar "/tools/.phive/phars/phpdocumentor-3.4.1.phar" (actual filesize mismatch on file "bin/phpdoc") in /tools/.phive/phars/phpdocumentor-3.4.1.phar on line 11

Fatal error: Uncaught Error: Failed opening required 'phar://phpdocumentor.phar/bin/phpdoc' (include_path='.:/usr/local/lib/php') in /tools/.phive/phars/phpdocumentor-3.4.1.phar:11
Stack trace:
#0 {main}
  thrown in /tools/.phive/phars/phpdocumentor-3.4.1.phar on line 11
image

Interestingly, phpDocumentor works when image is being built, but not when I run it on the built image. Perhaps a docker issue.

Originally posted by @jakzal in https://github.com/phpDocumentor/phpDocumentor/issues/3562#issuecomment-1709886494

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure when running the built Docker image and inspect how /tools/.phive/phars/phpdocumentor-3.4.1.phar is handled between image build and runtime. Compare the working build-time behavior with the corrupted phar reported in the error; done means phpDocumentor runs from the built image without the filesize mismatch or internal-corruption errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, php
Domain
devops, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.