新手求助：在Kubernetes中运行Oracle数据库Docker容器相关问题

Hey there! Since you're just starting out with Kubernetes using minikube, let's walk through how to deploy your app1, app2, and oracleDB containers step by step. I'll keep things practical and easy to follow—perfect for someone getting their feet wet with K8s.

Kubernetes needs access to your Docker images to create pods. Since you already have local containers, here's what to do:

• Convert your running containers to reusable images with docker commit (this saves your current container state as a deployable image):

  docker commit app1 your-local-tag/app1:v1
  docker commit app2 your-local-tag/app2:v1
  docker commit oracleDB your-local-tag/oracledb:v1
  

• Make sure minikube can access these local images. Run this command in your terminal to tell minikube to use your local Docker daemon (so you don't need to push images to a remote registry):

  eval $(minikube docker-env)
  

  Note: This only applies to your current terminal session—run it again if you open a new window.

First, we'll set up the database since app1 depends on it. We need two core Kubernetes resources: a Deployment to manage the database pod, and a Service to give it a stable address that other pods can reach.

Create an Oracle Deployment YAML (oracle-deployment.yaml) #

apiVersion: apps/v1
kind: Deployment
metadata:
  name: oracledb-deployment
spec:
  replicas: 1
  selector:
    matchLabels:
      app: oracledb
  template:
    metadata:
      labels:
        app: oracledb
    spec:
      containers:
      - name: oracledb
        image: your-local-tag/oracledb:v1
        ports:
        - containerPort: 1521
        resources:
          requests:
            memory: "4Gi"
            cpu: "2"
          limits:
            memory: "6Gi"
            cpu: "3"

Oracle is resource-heavy, so make sure your minikube has enough resources. Start minikube with extra capacity if you haven't already: minikube start --memory=8192 --cpus=4

Create an Oracle Service YAML (oracle-service.yaml) #

This gives the database a stable DNS name that app1 can use to connect (no hardcoding IPs!):

apiVersion: v1
kind: Service
metadata:
  name: oracledb-service
spec:
  selector:
    app: oracledb
  ports:
  - port: 1521
    targetPort: 1521
  type: ClusterIP

Apply these files to your cluster:

kubectl apply -f oracle-deployment.yaml
kubectl apply -f oracle-service.yaml

Wait for the pod to be ready—check status with kubectl get pods. Oracle can take 5-10 minutes to fully start up, so be patient!

For app1 (Depends on Oracle) #

First, update app1's configuration to point to the database using the service's DNS name: oracledb-service.default.svc.cluster.local (or just oracledb-service if you're using the default namespace). You can pass these details via environment variables in the deployment if your app supports it.

Create app1-deployment.yaml:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: app1-deployment
spec:
  replicas: 2
  selector:
    matchLabels:
      app: app1
  template:
    metadata:
      labels:
        app: app1
    spec:
      containers:
      - name: app1
        image: your-local-tag/app1:v1
        ports:
        - containerPort: 8080
        env:
        - name: DB_URL
          value: jdbc:oracle:thin:@oracledb-service:1521/ORCLPDB1
        - name: DB_USER
          value: your-db-username
        - name: DB_PASSWORD
          value: your-db-password

Adjust the DB_URL, DB_USER, and DB_PASSWORD to match your Oracle setup.

Create a service to access app1 from your desktop (we'll use NodePort):

apiVersion: v1
kind: Service
metadata:
  name: app1-service
spec:
  selector:
    app: app1
  ports:
  - port: 8080
    targetPort: 8080
    nodePort: 30001
  type: NodePort

For app2 (No Database Dependency) #

Create app2-deployment.yaml:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: app2-deployment
spec:
  replicas: 2
  selector:
    matchLabels:
      app: app2
  template:
    metadata:
      labels:
        app: app2
    spec:
      containers:
      - name: app2
        image: your-local-tag/app2:v1
        ports:
        - containerPort: 8080

And its service (app2-service.yaml):

apiVersion: v1
kind: Service
metadata:
  name: app2-service
spec:
  selector:
    app: app2
  ports:
  - port: 8080
    targetPort: 8080
    nodePort: 30002
  type: NodePort

Apply all app files to the cluster:

kubectl apply -f app1-deployment.yaml
kubectl apply -f app1-service.yaml
kubectl apply -f app2-deployment.yaml
kubectl apply -f app2-service.yaml

• Check if all pods are running:

  kubectl get pods
  

• View logs for any pod to debug startup issues:

  kubectl logs <pod-name>
  

• Access app1 and app2 from your desktop:
  • Get the minikube IP with minikube ip
  • Visit http://<minikube-ip>:30001 for app1, http://<minikube-ip>:30002 for app2
  • Or use minikube service app1-service to open it directly in your browser

• If pods are stuck in ImagePullBackOff, double-check that you ran eval $(minikube docker-env) before building/committing your images.
• Oracle pods might fail due to memory limits—adjust the resource requests/limits in the deployment if needed.
• Use kubectl describe pod <pod-name> to see detailed events if something goes wrong (this is your go-to debug tool!).

内容的提问来源于stack exchange，提问作者babs84