You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When executing the start command in Linux with docker desktop (as recommended), it works.
vip dev-env start --slug=acme-website
Actual Behavior
I get:
✕ Please contact VIP Support with the following information:
Error: Error: EACCES: permission denied, open '/home/johndoe/.local/share/vip/lando/scripts/add-cert.sh'
at exports.moveConfig (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/utils.js:165:13)
at /home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:119:32
at process.processImmediate (node:internal/timers:478:21)
From previous event:
at bootstrapEngine (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:116:39)
at bootstrapRouter (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:154:27)
at /home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:310:19
From previous event:
at /home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:310:8
From previous event:
at Lando.bootstrap (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:255:25)
at bootstrapLando (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/dist/lib/dev-environment/dev-environment-lando.js:191:17)
at async /home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/dist/bin/vip-dev-env-start.js:22:17
at async _args.default.argv (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/dist/lib/cli/command.js:444:11)
Steps to Reproduce the Problem
OS: Linux Ubuntu 22.04
Docker desktop: 4.29.0
VIP CLI: 2.39.0
For some reason, the target folder /home/johndoe/.local/share/vip/lando is owned by docker-desktop uid 100999 and gid 100999. I added created a group docker_share with gid 100999 but still get the error.
➜ acme-website git:(ABC-123) ls -la /home/johndoe/.local/share/vip/lando
total 76
drwxrwxr-x+ 10 100999 docker_share 4096 abr 21 23:42 .
drwxrwxr-x 5 johndoe johndoe 4096 abr 21 23:42 ..
drwxrwxr-x+ 2 100999 docker_share 4096 abr 21 23:43 cache
drwxrwxr-x+ 2 100999 docker_share 4096 abr 21 23:43 certs
drwxrwxr-x+ 3 100999 docker_share 4096 abr 21 23:42 compose
drwxrwxr-x+ 3 100999 docker_share 4096 abr 21 23:42 config
drwxrwxr-x+ 3 100999 docker_share 4096 abr 21 23:42 home
drwxrwxr-x+ 2 100999 docker_share 4096 abr 21 23:42 keys
drwxrwxr-x+ 3 100999 docker_share 4096 abr 21 23:42 proxy
drwxrwxr-x+ 2 100999 docker_share 4096 abr 21 23:42 scripts
The issue is entering here in the lando-core utils file.
The problem is that the node process is running by the host johndoe but the script is trying to do some file operations in files owned by 100999:100999.
That solved the first problem, now the process can open the files, but since the script tries to chmod here the operation is giving a new error:
✕ Please contact VIP Support with the following information:
Error: Error: EPERM: operation not permitted, chmod '/home/johndoe/.local/share/vip/lando/scripts/add-cert.sh'
at exports.moveConfig (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/utils.js:167:13)
at /home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:119:32
at process.processImmediate (node:internal/timers:478:21)
From previous event:
at bootstrapEngine (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:116:39)
at bootstrapRouter (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:154:27)
at /home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:310:19
From previous event:
at /home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:310:8
From previous event:
at Lando.bootstrap (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/node_modules/lando/lib/lando.js:255:25)
at bootstrapLando (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/dist/lib/dev-environment/dev-environment-lando.js:191:17)
at async /home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/dist/bin/vip-dev-env-destroy.js:23:17
at async _args.default.argv (/home/johndoe/.nvm/versions/node/v20.12.1/lib/node_modules/@automattic/vip/dist/lib/cli/command.js:444:11)
The text was updated successfully, but these errors were encountered:
Expected/Desired Behavior
When executing the start command in Linux with docker desktop (as recommended), it works.
Actual Behavior
I get:
Steps to Reproduce the Problem
OS: Linux Ubuntu 22.04
Docker desktop: 4.29.0
VIP CLI: 2.39.0
(Optional) Additional notes
Where is the issue?
For some reason, the target folder
/home/johndoe/.local/share/vip/lando
is owned by docker-desktop uid 100999 and gid 100999. I added created a groupdocker_share
with gid 100999 but still get the error.The issue is entering here in the lando-core utils file.
The problem is that the node process is running by the host
johndoe
but the script is trying to do some file operations in files owned by100999:100999
.I tried using setfacl like this:
That solved the first problem, now the process can open the files, but since the script tries to chmod here the operation is giving a new error:
The text was updated successfully, but these errors were encountered: