ghost setup fails on Alpine
See original GitHub issueIssue Summary
ghost production setup fails on Alpine with the following error:
Error occurred running command: ‘/bin/sh -c lsb_release -a’
Steps to Reproduce
- Install ghost-cli on alpine 6.11. I used a docker container and can supply the Dockerfile if needed.
- Run ghost install local
- Run ghost setup
Observe the error above is produced. lsb_release is not present on Alpine. Ghost needs to use an alternate method of obtaining this info on Alpine.
Technical details:
OS: Alpine 6.11
Debug Information:
Node Version: v6.11.0
Ghost-CLI Version: 1.0.0-beta.6
Environment: production
Command: 'ghost setup'
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Running Ghost in Alpine Linux - BrixIT Blog
A small tutorial for running Ghost on Alpine Linux ... except that it fails to set-up nginx since paths are different and you...
Read more >Gmail SMTP with Ghost docker (alpine) - Installation
Below is the error messages I got from the container's log via portainer: Error sending email: Failed to send email. Reason: queryA ETIMEOUT ......
Read more >Error connecting to database deploying Ghost docker image
Hello everyone! I am trying to deploy Ghost instance from latest dockerfile and such on getting the same error:
Read more >Building a Caddy container stack for easy HTTPS with Docker ...
Edit the docker compose file with your favourite editor and add this. ghost: image: ghost:4-alpine restart: unless-stopped environment: ...
Read more >arm64v8/ghost - Docker Image
Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Nice, that did it! I had been simply trying to force it with --url=http://0.0.0.0:8080
Closed by #318