Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign updeploy to kubernetes issue #294
Comments
|
Hi @DavidCamelo You need to have your instance on the same network that the database is onto to enable access via phpMyAdmin. |
|
Hi @williamdes Yes, my database is on the same network, I even have wordpress deploys and java application deploys pointing to that database. I also did a test only with docker pointing to an external database I have running on IP 54.68.2.230 and it works. I tried changing my deploy file and put only the PMA_HOST variable pointing to 54.68.2.230 but it still doesn't work apiVersion: apps/v1
kind: Deployment
metadata:
name: phpmyadmin
labels:
app: phpmyadmin
spec:
replicas: 1
selector:
matchLabels:
app: phpmyadmin
template:
metadata:
labels:
app: phpmyadmin
spec:
containers:
- name: phpmyadmin
image: phpmyadmin/phpmyadmin:5
ports:
- containerPort: 80
protocol: TCP
env:
- name: PMA_HOST
value: 54.68.2.230 |
|
Unfortunately I did not have the chance to try out kubernetes, It will take me some free time before I can run it on my workstation Here is another kubernetes issue, maybe fixed.: #217 Could you open a StackOverflow (or other) question to have some better and faster help and if a bug is found in your config we could fix it afterwards ? |
|
Sure I will try asking on StackOverflow, I'll keep you posted. |
|
@williamdes FYI this is my thread in StackOverflow in case you want to follow |
|
Hello, I also have the same problem deploying phpmyadmin to a kubernetes container. The logs are pointing to the same issue as you linked here: #217. Here are the logs from my pod, managed by Openshift (openshift's heart is 100% kubernetes): touch: cannot touch '/etc/phpmyadmin/config.user.inc.php': Permission denied AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.130.17.39. Set the 'ServerName' directive globally to suppress this message (13)Permission denied: AH00072: make_sock: could not bind to address [::]:80 (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down AH00015: Unable to open logs |
|
From the output the ports do not seem to bind |
|
Hi @oscarloop, I was trying in different ways to make it work and I couldn't do it, so I'm using the bitnami phpmyadmin image apiVersion: apps/v1
kind: Deployment
metadata:
name: phpmyadmin
labels:
app: phpmyadmin
spec:
replicas: 1
selector:
matchLabels:
app: phpmyadmin
template:
metadata:
labels:
app: phpmyadmin
spec:
containers:
- name: phpmyadmin
image: bitnami/phpmyadmin:latest
ports:
- containerPort: 8080
protocol: TCP
env:
- name: DATABASE_HOST
value: mysql-service |
|
They seem to re-build everything https://github.com/bitnami/bitnami-docker-phpmyadmin/blob/master/5/debian-10/Dockerfile @J0WI do you have some ideas about this issue ? |
|
@DavidCamelo can you share the complete log output? We can only see the |
|
@J0WI the log only shows the following, that's it.
|

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.


Hi,
I have the following configuration to deploy phpmyadmin to kubernetes.
When the pod goes up it doesn't start the apache, I have to run

service apache2 startafter this I check the phpmyadmin and see that it doesn't take the environment variables defined to connect to the databaseCould you help me with this problem? thanks in advance!