[Bug] Docker fails to build and setup WordPress properly on Unbuntu Linux OS

Open
#94 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, docker-compose, shell, ubuntu, wordpress

Research direction

Start with config/www-data_startupservice at line 5 and reproduce the failure with docker compose up on Ubuntu 20.04. Trace the reported sudo password error during the WordPress container setup, then verify that a fresh Docker build and setup completes successfully on Linux without breaking the stated Mac and Windows expectation.

Written by the indexing model from the issue text.

Description

💻 aspect: code 🚦 status: awaiting triage 🛠 goal: fix 🟨 priority: medium

Description

When attempting a fresh build within a Linux environment, the WordPress container fails to adequately run its setup, leaving the environment unusuable.

Reproduction

run docker compose up

error produced:


index-web         | sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
index-web         | sudo: a password is required

Expectation

The Docker setup should build successfully on Mac, Windows, and Linux operating systems

Environment

  • OS: Ubuntu v20.04.6 LTS (Focal Fossa)

Additional context

This was tested via a devcontainer, but should be present on a regular Linux install, since the devcontainer emulates that particular environment similarly.

I'm guessing the Operating System is not adequately recognizing/applying www-data_startupservice:line 5

Resolution

  • I would be interested in resolving this bug.
Dominant language
Shell
Stars
8
Forks
5
Avg merge
51m
Merged PRs (30d)
2

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from creativecommons/index-dev-env

All issues in creativecommons/index-dev-env

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.