magento / magento/magento-cloud-docker
unable to provide the crypt key when using the existing database
Open
Nobody has claimed this yet.
Progress: ready for grooming
- Dominant language
- PHP
- Stars
- 277
- Forks
- 187
- PR merge metrics
- No merged PRs in 30d
Description
Hi Support,
I am creating the local instance with docker setup and used the database entry point to use the existing database for the application, when running the deploy command throwing the error like Missing Crypt key for upgrading magento, can you suggest how we can provide crypt key on docker configuration?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker configuration and database entry point used by the deploy command, then trace where the existing database's crypt key is expected. Done means the deployment path clearly accepts or reports the required crypt key when using an existing database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100