Able to run CLI build, but as another userid when copy to another directory results in runtime error

Certainly! Here’s how you can approach and solve the problem described:

---

Problem Recap

• You package a CLI PHP application into a .phar file on Ubuntu (presumably with box), and it runs for one user just fine.
• When you copy the .phar file to another directory and/or try to run it as a different user, you get errors like:

PHP Notice:  require(): zlib: data error ...
PHP Warning:  require(phar://...): Failed to open stream: phar error: internal corruption of phar ... (actual filesize mismatch on file ...)

---

Explanation

These errors generally mean that the .phar file is corrupted or unreadable to PHP’s Phar extension. Typical causes in scenarios like yours are:

1. File corruption during copy: Sometimes copying files between filesystems or using the wrong tool/command can mangle binary files.
2. Permissions: The new user may not have read access, or the phar may have been modified in such a way that its verification fails.
3. Filesystem issues: Filesystems with limits or special behavior may affect the file integrity (e.g., mounting with noexec or copying between ext4 ↔ FAT).
4. SELinux/AppArmor: These can restrict file access for different users or contexts.

---

Solution Steps

1. Verify File Permissions

Make sure that the file is readable by the intended user:

ls -l your-phar-file.phar

If necessary, set permissions so others can read it:

chmod a+r your-phar-file.phar

---

2. Correct Copying Method

• Always use cp or rsync for binary files.
• E.g.:

cp your-phar-file.phar /path/to/other/directory/

or, for copying to another user:

sudo cp your-phar-file.phar /home/otheruser/
sudo chown otheruser:otheruser /home/otheruser/your-phar-file.phar

• Avoid copying with cat, echo, or via text editors.

---

3. Verify File Integrity after Copying

Immediately after copying, compare hashes:

sha256sum original/your-phar-file.phar
sha256sum /path/to/other/directory/your-phar-file.phar

Hashes should be identical. If not, the file was corrupted during the copy.

---

4. Do Not Edit/Transfer with Text Tools

• If the .phar went through a tool like nano, vim, or was transferred via FTP in text mode, it is likely to be corrupted. Only transfer .phar files using binary-safe methods (scp, rsync, cp).

---

5. Check for SELinux/AppArmor

If you are on a system using SELinux or AppArmor, they may block access. Try as root or with setenforce 0 (on SELinux, for testing purposes only—not permanent!) to see if the problem goes away.

---

6. Rebuild the Phar file if Necessary

If the .phar is corrupted, rebuild it:

box compile

or whatever your build command is.

---

Example Commands

# For copy to another user:
cp myapp.phar /home/otheruser/
chown otheruser:otheruser /home/otheruser/myapp.phar

# Ensure permissions:
chmod 755 /home/otheruser/myapp.phar

# Verify hash:
sha256sum myapp.phar /home/otheruser/myapp.phar

---

Summary Table

Step	Command/Action
Check Permissions	ls -l / chmod a+r ...
Safe Copy	cp or rsync
Hash Verification	sha256sum both files
Check SELinux	sestatus / setenforce 0
Rebuild PHAR	box compile (or your build tool)

---

If you follow these steps, you should be able to determine and fix the cause of the "phar internal corruption" error when moving or using your PHAR file as another user.

---

Additional Note:
For .phar files, file permissions and file integrity are crucial. The PHP Phar extension will refuse to execute a PHAR it suspects is tampered with or corrupted.

---

If you need a code snippet or script for quick verification/checking, here's a Bash example:

# Usage: check-phar.sh /path/to/phar
file="$1"
php -r "if (Phar::canOpenPhar('$file')) { echo 'Phar OK\n'; } else { echo 'Phar BAD\n'; }"

---

Let me know if you still get errors after double-checking these steps!