Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Console container startup issue #666

Open
kierenevans opened this issue Feb 15, 2022 · 0 comments · May be fixed by #741
Open

Console container startup issue #666

kierenevans opened this issue Feb 15, 2022 · 0 comments · May be fixed by #741
Labels
bug Something isn't working
Milestone
1.4.0

Comments

@kierenevans
Copy link
Contributor

For a sylius project (symfony harness), in enable.sh we have:

docker-compose up -d --build console
docker-compose exec -u build console app build

The frontend build that happens after composer install fails when there's nothing to download via composer:

■ > yarn install
Command failed. stderr:
Error: EACCES: permission denied, open '/home/build/.config/yarn'
    at Object.openSync (fs.js:443:3)
    at readFileSync (fs.js:343:35)
    at /home/build/.nvm/versions/node/v10.24.1/lib/node_modules/yarn/lib/cli.js:101466:58
    at Array.map (<anonymous>)
    at parseRcPaths (/home/build/.nvm/versions/node/v10.24.1/lib/node_modules/yarn/lib/cli.js:101464:78)
    at Object.findRc (/home/build/.nvm/versions/node/v10.24.1/lib/node_modules/yarn/lib/cli.js:101478:10)
    at getRcConfigForCwd (/home/build/.nvm/versions/node/v10.24.1/lib/node_modules/yarn/lib/cli.js:56957:74)
    at /home/build/.nvm/versions/node/v10.24.1/lib/node_modules/yarn/lib/cli.js:92827:56
    at Generator.next (<anonymous>)
    at step (/home/build/.nvm/versions/node/v10.24.1/lib/node_modules/yarn/lib/cli.js:310:30)
----------------------------------
Full logs are accessible in the console container at path :-
  stdout: /tmp/my127ws-stdout.txt
  stderr: /tmp/my127ws-stderr.txt

Introducing a sleep 1 during these two commands lets it complete successfully.

I think we need to wait for the usermod/chown that happens in entrypoint.dynamic.sh to finish upon console container startup, before we continue onto the app build step.
@kierenevans kierenevans added the bug Something isn't working label Feb 15, 2022
@kierenevans kierenevans added this to the 1.3.0 milestone Feb 15, 2022
@kierenevans kierenevans changed the title Console container startup condition Console container startup issue Feb 15, 2022
@andytson-inviqa andytson-inviqa modified the milestones: 1.3.0, 1.4.0 Apr 8, 2022
@marcomc marcomc linked a pull request Jan 26, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
1.4.0
Development

Successfully merging a pull request may close this issue.

Fix console container startup issue inviqa/harness-base-php
2 participants
@kierenevans @andytson-inviqa