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..
Hello team, I new here in Spryker, I have done the installation with Docker in Windows, and I want t
Comments
-
@florian.scholz PS C:\Users\ChristosBoursinos> wsl -l -v
NAME STATE VERSION- Ubuntu Running 2
PS C:\Users\ChristosBoursinos>
0 - Ubuntu Running 2
-
@U012PCVT2DB also the same for me
0 -
@florian.scholz Running generator
PHP Warning: file_put_contents(/data/deployment/project.yml): failed to open stream: Permission denied in /data/deploy-file-generator/src/Processor/Executor/PostExecutors/ExportDeployFileTransferToYamlExecutor.php on line 45
genrsa: Can't open "/data/deployment/context/ssh/private.key" for writing, Permission denied0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
ok. maybe because of the now changed sync mode.
Lets try the following:
1. revert the changes
2.docker/sdk clean
3.rm -Rf docker/deployment/default
4. apply the changes again
5.docker/sdk boostrap deploy.dev.yml
6.docker/sdk up --build --assets --data
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
maybe try step 3 first; maybe its enough
0 -
didn't do anything 😞
0 -
@florian.scholz still the same error
0 -
The error is coming from the fix in the code of platform
0 -
also applying the complete path, you mentioned produces the error
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
what is strange that the bootstrap worked for you before. The exception i normally just saw together with permission problems of the environment overall - the solution was to follow this one: https://docs.docker.com/engine/security/rootless/ - yet this does not make sense ein your case
0 -
The change here produces the error https://github.com/spryker/docker-sdk/pull/341/files
0 -
So I removed the extra code and just left "linux"
0 -
and it's building
0 -
So the line of code is buggy
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
maybe it is not prepared to be used like that^^ important is that for the windows detected OS it does not use docker-sync and not mutagen but the native sync
0 -
I am waiting the build to finish
0 -
So then I will try to setup the debug again.
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
tomorrow i will also validate on my end with a clean windows machine i’ll get access to
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
i think the goal is to have
$_SERVER['SPRYKER_XDEBUG_HOST_IP']
properly set ashost.docker.internal
0 -
Also we will going to need a way to run tests through phpstorm, but this is another conversation
0 -
Just try to play with the debugger first
0 -
@florian.scholz can you share to us some screenshots of what you have as settings in you phpStorm to check what might be the difference with us
0 -
This open issue might affects the process? https://github.com/spryker/docker-sdk/issues/376
0 -
well, after some bad code-changes i can confirm that, when the $_SERVER['SPRYKER_XDEBUG_HOST_IP'] is set to 'host.docker.internal' it will debug, so we will need to find the correct way to get it there... 😞
0 -
I have a whole of team that will start writing in Spryker from the next weeks, so until we found a solution we are not going to have debugger. 😕
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
@U04HZ4BLVMM Yes, this is exactly the problem which should be fixed with the change in platform.sh - and which we merged already once into master.
Sadly we had to revert the fix because some other pieces were not working anymore because they used the wrong detected OS.
Tomorrow I will try it out by myself with a windows machine; tomorrow afternoon I can tell you more. In the meantime it would help if you comment in the linked github issue that you have the same problem.
0 -
Thanks Looking forward!
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
So guys… I checked now with an windows 11 + WSL2 setup. When i fix the docker/bin/platform.sh as mentioned and have the deploy.dev.yml as the following it works for me:
docker: ssl: enabled: false redirect: true testing: store: DE debug: enabled: true xdebug: enabled: true mount: native: platforms: - linux - windows mutagen: platforms: - macos
0 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,072 ⚖️ - Guardians (admin)
an alternative would be step 7 of the following instruction: https://docs.spryker.com/docs/scos/dev/setup/installing-spryker-with-docker/installation-guides/installing-in-development-mode-on-windows.html#i[…]s
0 -
I am using W10 + WSL2 😞
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 74 Spryker News
- 911 Developer Corner
- 771 Spryker Development
- 87 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 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
- 69 Spryker Safari Questions
- 50 Random