[#48363] - [5.4][codespaces] Change command to start Apache in docker-compose
- Pending
- Medium
- Build: 5.4-dev
- Draft PR
- # 48363
- Diff
- alikon:patch-7
User tests: Successful: Unsuccessful:
Pull Request resolves # .
- I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.
Summary of Changes
Change command to start Apache in docker-compose from sleep infinity to apache2-foreground
Testing Instructions
open a codespaces
Actual result BEFORE applying this Pull Request
sometimes apache doesn't start
Expected result AFTER applying this Pull Request
apache starts
Link to documentations
Please select:
-
Documentation link for guide.joomla.org:
-
No documentation changes for guide.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
I have tested this item 🔴 unsuccessfully on ae978af
I tested this PR twice in GitHub Codespaces. Both times, the environment built successfully and the Joomla installation page loaded via port 80, but the container crashed and became unavailable immediately after opening the site.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48363.
Joomla installation page
then something has going wrong on yuor side , after finished the post create it will open the already installed joomla hoempage
Hi @alikon,
I tested this locally and found a stable way to auto-start Apache without causing the container to crash.
Changing command to apache2-foreground in docker-compose.yml binds the container lifecycle directly to Apache (which shuts down the whole Codespace if Apache exits or reloads).
Instead, keeping docker-compose.yml untouched and adding "postStartCommand": "service apache2 start" to .devcontainer/devcontainer.json seamlessly launches Apache in the background on start while keeping the container fully stable.
Here is the updated section for .devcontainer/devcontainer.json:
"postStartCommand": "service apache2 start",
"customizations": {
I have tested this item 🔴 unsuccessfully on ae978af
I tested this PR twice in GitHub Codespaces. Both times, the environment built successfully and the Joomla installation page loaded via port 80, but the container crashed and became unavailable immediately after opening the site.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48363.