What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi guys. I am having problems with getting suite to build via docker with the deploy.dev.yml. I b2c-
Hi guys. I am having problems with getting suite to build via docker with the deploy.dev.yml. I b2c-demo builds and runs fine with the deploy.dev.yml and the deploy.yml also works fine in both shops.
chmod: changing permissions of '/data/config/Zed/dev_only_private.key': Operation not permitted chmod: changing permissions of '/data/config/Zed/dev_only_public.key': Operation not permitted Loading composer repositories with package information Installing dependencies (including require-dev) from lock file Package operations: 1035 installs, 0 updates, 0 removals [RuntimeException] /data/vendor does not exist and could not be created. install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>]...
Comments
-
Hello Thomas,
What OS are you on?
0 -
Debian
0 -
it seems it is permission issue.
Please, runid
0 -
I assume your problem is similar to https://sprykercommunity.slack.com/archives/CMYFJCG2E/p1593781137141700
0 -
sure seems like it. Strange. I also tried as root:
uid=0(root) gid=0(root) groups=0(root)
0 -
Root is not a good choice.
0 -
Are you able to use user 1000:1000 ?
0 -
yes, sure, that is what i used before resorting to root π unfortunately, it results in the same error
0 -
@ULYHPR789 i will take a look into the thread you linked and tinker around myself. it is not an urgent issue. i will update this thread here, if i come across a solution. Thanks for the input
0 -
ok. Thank you for sharing issues.
0 -
if support needed let me know π
0 -
Thanks for the offer. So this worked for me now: building using deploy.dev.yml failed for me with a permissions error described above. I tried strarting from a clean slate, but to no avail. In the end, after receiving another permission error during building, i used
chown -R 1000:1000
on the suite root directory and started the whole build process again. To my surprise everything worked after that.0 -
Did you set permission locally?
0 -
before the chown i did not set up any special permissions whatsoever if that is what you mean
0 -
I mean on host or in container?
0 -
on host
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 929 Developer Corner
- 787 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random