Ghost image not usable anymore

Hi all,
I just noticed that the "ghost" image is not usable anymore. It will deploy but spinning the pod will fail:
`[023-03-27 09:59:34] INFO Ghost is running in production...
[2023-03-27 09:59:34] INFO Your site is now available on http://localhost:2368/
[2023-03-27 09:59:34] INFO Ctrl+C to shut down
[2023-03-27 09:59:34] INFO Ghost server started in 0.785s
[2023-03-27 09:59:34] ERROR connect ECONNREFUSED 127.0.0.1:3306
connect ECONNREFUSED 127.0.0.1:3306
"Unknown database error"
Error ID:
500
Error Code:
ECONNREFUSED
Error: connect ECONNREFUSED 127.0.0.1:3306
at /var/lib/ghost/versions/5.40.1/node_modules/knex-migrator/lib/database.js:57:19
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
[2023-03-27 09:59:34] WARN Ghost is shutting down
[2023-03-27 09:59:34] WARN Ghost has shut down
[2023-03-27 09:59:34] WARN Your site is now offline
[2023-03-27 09:59:34] WARN Ghost was running for a few seconds
`
It seems that a running mandatory mysql/mariaDB is hardwired into the images code.
Not sure on how to proceed here.
Either use a different image/app (e.g. nginx, git, hlds ...) or
re-write the helm manifest so a mariaDB will also be deployed or
fix the image so if no DB is available the pod will still spin up ... ?
Comments
-
So, ... since NOBODY
replied to my question, I had to figured it out by myself.
So here is the yaml that will deploy a pod with two containers ghost and mariaDB.However, the Pod will come up successfully but will fail (after a minute or so) because mariaDB creates a fresh and completely empty database, thus ghost can't read anything from it.
apiVersion: apps/v1 kind: Deployment metadata: name: sadako spec: # specification for deployment resource selector: matchLabels: app: sadako template: metadata: labels: app: sadako spec: # specification for Pods containers: - name: mariadb image: bitnami/mariadb env: - name: MARIADB_ROOT_PASSWORD value: secret - name: ghost image: bitnami/ghost ports: - containerPort: 80 env: - name: ALLOW_EMPTY_PASSWORD value: "yes"
0 -
Hi @mag1,
Would you be able to provide the section in the lab guide where the ghost image is referenced?
Regards,
-Chris0 -
I am stumbleing over the same error as @mag1 in the course material. I have jet to view the lab guides. I am following along in the Chapter 11 Ingress of the course in the slide "Creating an Ingress Rule".
It contains the following 2 commands:
$ kubectl run ghost --image=ghost
$ kubectl expose deployments ghost --port=2368The seccond one also fails as the first one does not create a deployment, it only creates a pod.
Hope this helps.
And thanks @mag1 for creating the YAML, will use/replikate it now.Have a nice Easter Weekend!
Best Regards,
McDueerkop
0 -
Hi @mag1
Sadly i could not "plug & play" your template into my env.
I always got an error message that the ghost image could not connect to the mariadb instance even though it was running in the same pod.I made some modifications:
- Use the official docker images.
- Pass the development variable into the ghost image, to ensure it starts up as a dev enviornment.
Here is the complete yml for review:
apiVersion: apps/v1 kind: Deployment metadata: name: ghost spec: selector: matchLabels: app: ghost template: metadata: labels: app: ghost spec: containers: - name: mariadb image: mariadb env: - name: MARIADB_ROOT_PASSWORD value: my-secret-pw - name: ghost image: ghost ports: - containerPort: 2368 env: - name: NODE_ENV value: development
Best Regards,
McDueerkop
0 -
Hi @mag1 and @mcdueerkop,
I would recommend following exercises from the lab guide for hands-on experience. Some of the illustrative commands from the lectures section may not work if applied directly as presented.
Regards,
-Chris0 -
@chrispokorni said:
Hi @mag1 and @mcdueerkop,I would recommend following exercises from the lab guide for hands-on experience. Some of the illustrative commands from the lectures section may not work if applied directly as presented.
Regards,
-ChrisSee, that's actual the problem. Those exercises include "packages" like ghost and therefore fail without a hint from the text.
0 -
Hi @mag1,
Would you be able to provide the lab exercise number and step number where the ghost image is referenced and fails?
Regards,
-Chris0 -
Hi, sorry for the late reply.
Indeed I couldn't find any appearances of "ghost" in any lab-exercise (pdf documents).
But if you go to chapter 7 (Managing State with Deployments) Section: Managing State with Deployments -> Deployment Rollbacks (page: 10) ... here it is used multiple times.0 -
I just hit the same issue. The text of Chapter 11, "Creating an Ingress Rule", sets a clear expectation with the reader that the code presented should work.
To get exposed with ingress quickly, you can go ahead and try to create a similar rule as mentioned on the previous page. First, start a ghost deployment and expose it with an internal ClusterIP service. See the following commands:
$ kubectl run ghost --image=ghost
$ kubectl expose deployments ghost --port=2368
If this should not be taken literally, it should not use literal language issuing directives for the reader to follow along. The fact that this has been a known issue for a year and the paid course still includes the example with the bug is frustrating.
0
Categories
- All Categories
- 240 LFX Mentorship
- 240 LFX Mentorship: Linux Kernel
- 815 Linux Foundation IT Professional Programs
- 366 Cloud Engineer IT Professional Program
- 184 Advanced Cloud Engineer IT Professional Program
- 83 DevOps Engineer IT Professional Program
- 129 Cloud Native Developer IT Professional Program
- 142 Express Training Courses & Microlearning
- 142 Express Courses - Discussion Forum
- Microlearning - Discussion Forum
- 6.5K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 72 LFC131 Class Forum
- 49 LFD102 Class Forum
- 234 LFD103 Class Forum
- 21 LFD110 Class Forum
- 29 LFD121 Class Forum
- LFD123 Class Forum
- LFD125 Class Forum
- 16 LFD133 Class Forum
- 6 LFD134 Class Forum
- 18 LFD137 Class Forum
- 70 LFD201 Class Forum
- 3 LFD210 Class Forum
- 2 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 1 LFD233 Class Forum
- 2 LFD237 Class Forum
- 23 LFD254 Class Forum
- 719 LFD259 Class Forum
- 111 LFD272 Class Forum - Discontinued
- 3 LFD272-JP クラス フォーラム
- 13 LFD273 Class Forum
- 227 LFS101 Class Forum
- 1 LFS111 Class Forum
- 2 LFS112 Class Forum
- 1 LFS116 Class Forum
- 3 LFS118 Class Forum
- LFS120 Class Forum
- 1 LFS142 Class Forum
- 2 LFS144 Class Forum
- 3 LFS145 Class Forum
- 4 LFS146 Class Forum
- 15 LFS148 Class Forum
- 15 LFS151 Class Forum
- 1 LFS157 Class Forum
- 61 LFS158 Class Forum
- LFS158-JP クラス フォーラム
- 4 LFS162 Class Forum
- 1 LFS166 Class Forum
- 2 LFS167 Class Forum
- 3 LFS170 Class Forum
- 1 LFS171 Class Forum
- 1 LFS178 Class Forum
- 2 LFS180 Class Forum
- 1 LFS182 Class Forum
- 3 LFS183 Class Forum
- 30 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 2 LFS201-JP クラス フォーラム
- 20 LFS203 Class Forum
- 109 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- 2 LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 53 LFS241 Class Forum
- 43 LFS242 Class Forum
- 37 LFS243 Class Forum
- 16 LFS244 Class Forum
- 1 LFS245 Class Forum
- LFS246 Class Forum
- LFS248 Class Forum
- 63 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 156 LFS253 Class Forum
- LFS254 Class Forum
- 2 LFS255 Class Forum
- 6 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.3K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 113 LFS260 Class Forum
- 161 LFS261 Class Forum
- 41 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 21 LFS267 Class Forum
- 18 LFS268 Class Forum
- 29 LFS269 Class Forum
- 7 LFS270 Class Forum
- 199 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 2 LFS147 Class Forum
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 16 LFW111 Class Forum
- 262 LFW211 Class Forum
- 176 LFW212 Class Forum
- 15 SKF100 Class Forum
- SKF200 Class Forum
- 2 SKF201 Class Forum
- 797 Hardware
- 198 Drivers
- 68 I/O Devices
- 37 Monitors
- 96 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 83 Storage
- 761 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 149 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 355 Ubuntu
- 463 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 91 Linux Security
- 78 Network Management
- 101 System Management
- 46 Web Management
- 55 Mobile Computing
- 18 Android
- 28 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 364 Off Topic
- 115 Introductions
- 170 Small Talk
- 26 Study Material
- 518 Programming and Development
- 304 Kernel Development
- 211 Software Development
- 1.1K Software
- 211 Applications
- 180 Command Line
- 3 Compiling/Installing
- 405 Games
- 311 Installation
- 78 All In Program
- 78 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)