resolve : lstat /Users/jim/Documents/PR-PRISM/.wappler/targets/development/db: no such file or directory
error message displayed on local development, tried refreshing db and tables no joy.
should I copy the ‘Dockerfile‘ from a backup of the project and drop it into the
/Users/jim/Documents/PR-PRISM/.wappler/targets/development/db/ folder
contents of the dockerfile-
FROM mysql:8.0
COPY db_init/ /docker-entrypoint-initdb.d/
I see some strange line in the file, which not sure how it got there:
build:
context: '.'
dockerfile: 'db/Dockerfile'
are you 100% sure this was generated entirely by wappler and not by editing the file by hand or using a third party tool, AI or anything else than Wappler?
I'll just interject. Although my utility was used (after two or three hours of Wappler issues) it doesn't change any Wappler Project files or insert nefarious lines nor adjust Targets. It creates its own directory where it also then creates its own files that it uses (entirely independent of Wappler, and they are just for connection and deployment). Just want to remove that from speculation.
Checking what WDP generates and whether it modifies Wappler project files or adds db/Dockerfile build blocks.
WDP does not add db/Dockerfile or a DB build: block
In generated wdp/{profile}/docker-compose.deploy.yml, the database service (when Step 3 is “managed” DB) uses official images only:
PostgreSQL: image: postgres:16-alpine
MySQL: image: mysql:8.0
There is no build: section on db, and WDP never creates a db/Dockerfile or db/ folder.
The only build: WDP generates is for the app service:
build:
context: '.'
dockerfile: wdp/{profile}/Dockerfile.deploy
({profile} is your deployment profile name, e.g. production.)
So this pattern is not from WDP:
build:
context: '.'
dockerfile: 'db/Dockerfile'
That’s typical of Wappler’s own Docker target / project layout, not the WDP wizard.
Hi Teodor,
I wouldn’t have created that, as I reported earlier it seems that Wappler has been creating duplicate folders and spurious files in the .wappler/ folder.
This seems to have been resolved since I reinstalled wappler and moved the project away from it’s original location to prevent any external factors that may have caused any of those issues.
I don't think these lines are generated by default by Wappler, @George can explain this in more details.
Meanwhile what you can try is (backup your .yml file first!) and remove these lines:
build:
context: '.'
dockerfile: 'db/Dockerfile'
try building after that and see if the error is gone.
