codebuild fails in d middle of the Dockerfile
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, php, redis
- Domain
- build-system, devops
Research direction
Start with the Dockerfile section that installs PHP Redis and run the image build to capture the full apt-get error behind exit code 100. Check which command in this chained step fails; done means the Docker build completes and the Redis extension is installed without leaving the temporary build files.
Written by the indexing model from the issue text.
Description
Install PHP Redis
RUN apt-get install -y autoconf wget build-essential --ignore-engines &&
wget https://pecl.php.net/get/redis-5.3.7.tgz &&
tar xzf redis-5.3.7.tgz &&
cd redis-5.3.7 &&
phpize &&
./configure &&
make &&
make install &&
echo "extension=redis.so" >> /usr/local/etc/php/php.ini-development &&
echo "extension=redis.so" >> /usr/local/etc/php/php.ini-production &&
apt-get purge --autoremove -y autoconf wget build-essential &&
cd .. &&
rm redis-5.3.7.tgz &&
rm -rf redis-5.3.7
while executing this command codebuild fails and shows some error
ERROR: failed to solve: process "/bin/sh -c apt-get install -y autoconf wget build-essential --ignore-engines && wget https://pecl.php.net/get/redis-5.3.7.tgz && tar xzf redis-5.3.7.tgz && cd redis-5.3.7 && phpize && ./configure && make && make install && echo "extension=redis.so" >> /usr/local/etc/php/php.ini-development && echo "extension=redis.so" >> /usr/local/etc/php/php.ini-production && apt-get purge --autoremove -y autoconf wget build-essential && cd .. && rm redis-5.3.7.tgz && rm -rf redis-5.3.7" did not complete successfully: exit code: 100
pls help me to resolve this issue if someone knows
- Dominant language
- JavaScript
- Stars
- 3.1k
- Forks
- 6.4k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/getting-started
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
docker/getting-started#481 · 2 comments · 5 reactions ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
docker/getting-started#394 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
docker/getting-started#494 ·
-
Chat Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
docker/getting-started#482 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 1/100
docker/getting-started#477 ·
All issues in docker/getting-started
Similar issues
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
DavidAnson/markdownlint-cli2#940 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100