Hi guys. I am having problems with getting suite to build via docker with the deploy.dev.yml. I b2c-

Thomas Lehner

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>]...

sprymiker

Hello Thomas,

What OS are you on?

Thomas Lehner

Debian

sprymiker

it seems it is permission issue.
Please, run
id

sprymiker

I assume your problem is similar to https://sprykercommunity.slack.com/archives/CMYFJCG2E/p1593781137141700

Thomas Lehner

sure seems like it. Strange. I also tried as root:

uid=0(root) gid=0(root) groups=0(root)

sprymiker

Root is not a good choice.

sprymiker

Are you able to use user 1000:1000 ?

Thomas Lehner

yes, sure, that is what i used before resorting to root 🙂 unfortunately, it results in the same error

Thomas Lehner

@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

sprymiker

ok. Thank you for sharing issues.

U015AQKSZJ7

if support needed let me know 🙂

Thomas Lehner

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.

sprymiker

Did you set permission locally?

Thomas Lehner

before the chown i did not set up any special permissions whatsoever if that is what you mean

sprymiker

I mean on host or in container?

Thomas Lehner

on host