Containers and Kubernetes

Get Involved. Join the Conversation.


  • 1-9 of 9
  • Sayan Malakshinov
    Containers based on Windows15.0
    Topic posted July 31, 2018 by Sayan Malakshinov, tagged Containers, Docker, Kubernetes 
    Containers based on Windows

    One of our main applications requires IIS with .Net Framework, which is platform-dependent and requires docker host on Windows, but Oracle Cloud Container Service and Oracle Application Container Service currently support Linux hosts only.

    If we try to deploy official docker dotnet-framework image by Microsoft we get error:

    ERROR Failed to pull image microsoft/dotnet-framework-samples:aspnetapp due to error no supported platform found in manifest list
    Error: no supported platform found in manifest list

     How can we ask Oracle to add containers based on Windows?

  • Shivin Vijai
    Oracle Container Registry support signed images?14.5
    Topic posted August 2, 2018 by Shivin VijaiSilver Medal: 2,000+ Points, tagged Containers, Docker, Kubernetes, Registry 
    Oracle Container Registry support signed images?
    I need to deploy (push and pull) signed images on Kubernetes

    As far I know Oracle Container Registry currently do not support signed images. Is it true? Is there any good workarounds for that. What is the gap from a normal kubernetes deployment using a unsigned image?

    I need to have content trust in docker images. Content trust gives me the ability to verify both the integrity and the publisher of all the data received from a registry over any channel.

    I am looking this for a production set.



  • Shivin Vijai
    Can I run Fn on OKE14.3
    Topic posted August 20, 2018 by Shivin VijaiSilver Medal: 2,000+ Points, tagged Containers, Docker, Kubernetes, Tip 
    Can I run Fn on OKE

    Can I run Fn on OKE?

  • John K
    Deploying a basic node app to the cloudAnswered65.0
    Topic posted September 6, 2019 by John KGreen Ribbon: 100+ Points, tagged Containers, Docker, Kubernetes 
    Deploying a basic node app to the cloud

    Apologies for the basic question but I just signed up for a trial cloud account and want to deploy a simple hello world node app to the cloud. Even Oracle's documentation seems dated as everything I find online references Application Container Cloud which I don't see in my list of trial account applications. Nor do I see anything related to Container Cloud. Does anyone have a tutorial or how-to doc that I could follow to learn how to deploy a simple node app. Thanks in advance for pointing me in the right direction.

  • Joydeepta Bhattacharjee
    Pod to Pod communication with service name Should be...15.0
    Topic posted July 20, 2019 by Joydeepta BhattacharjeeRed Ribbon: 250+ Points, tagged Containers, Docker, Kubernetes, Tip 
    Pod to Pod communication with service name Should be followed with Ingress Resource to realise a decouple connection
    Instead of accessing IP which changes with deployment I would like to access pod deployment with service created which is not working in OCI OKE setup

    kubectl describe services kube-dns --namespace kube-system


    Name:              kube-dns
    Namespace:         kube-system
    Selector:          k8s-app=kube-dns
    Type:              ClusterIP
    Port:              dns  53/UDP
    TargetPort:        53/UDP
    Port:              dns-tcp  53/TCP
    TargetPort:        53/TCP
    Session Affinity:  None
    Events:            <none>
    [opc@test ~]$


    , kubectl describe svc my-api 

    [opc@test ~]$ kubectl describe svc springbootapp-demo-service
    Name:                     springbootapp-demo-service
    Namespace:                default
    Labels:                   <none>
    Annotations:              <none>
    Selector:                 app=app
    Type:                     LoadBalancer
    LoadBalancer Ingress:
    Port:                     <unset>  80/TCP
    TargetPort:               8035/TCP
    NodePort:                 <unset>  30963/TCP
    Endpoints:      ,, + 1 more...
    Session Affinity:         None
    External Traffic Policy:  Cluster
    Events:                   <none>


    Now  when i exec(kubectl exec -it  **Pod) to a pod and wget the other pod by FQDN it's not reached. I also connected a busy-box image to debug the kube-dns networking between pods. 

    Exec to the pod takes to prompt as  kubectl exec -it nodejs-deployment-6bffdcb99c-lf8gn sh and tried to wget below end point dummy but unreachable though IP is looked up.

     wget http://springbootapp-demo-service/demo/test
    Connecting to springbootapp-demo-service(

    This has been fixed now by renaming the selector lebel in deployment yml to unique name as they are in default name space 

  • Ranjans
    cx_Oracle.DatabaseError: DPI-1047 while connecting to...
    Topic posted September 12, 2019 by Ranjans Red Ribbon: 250+ Points, tagged Containers, Docker 
    cx_Oracle.DatabaseError: DPI-1047 while connecting to cx_Oracle on docker

    Hi ,

    I have written my function in python. When I am trying to invoke the function. I am getting the below error.  I have attached the Dockerfile also. Any suggestions.


    fn invoke appname func1

    cx_Oracle.DatabaseError: DPI-1047: Cannot locate a 64-bit Oracle Client library: " cannot open shared object file: No such file or directory". See for helpC


  • Ranjans
    connect to adwc with fn(function)
    Topic posted September 11, 2019 by Ranjans Red Ribbon: 250+ Points, tagged Containers, Docker 
    connect to adwc with fn(function)
    connect to adwc with fn (function)

    Hi Everyone,

    Can anyone ,please suggest me in the below .
    I wanted to run my python code through oracle serverless computing( through fn function)
    Therefore I am facing challenge in connecting to adwc database with fn.
    In order to connect I need a init image file in python or Dockerfile in python.
    Can anyone suggest me, how to connect to autonomous database using fn .



  • Ranjans
    unable to invoke the function in oci1
    Topic posted August 22, 2019 by Ranjans Red Ribbon: 250+ Points, tagged Containers, Docker 
    unable to invoke the function in oci
    unable to invoke the function in oci

    As per Python SDK , when I am importing the config value, the function is not getting invoke and is error out . The function has been built using python .

    The following command is used to invoke the function

    fn invoke  app_py pythonfn



    import json
    import io
    import oci
    from oci.config import from_file
    import sys
    from fdk import response

    config = from_file(profile_name="DEFAULT")

    def handler(ctx, data: io.BytesIO=None):

            body = json.load(data)

  • Joydeepta Bhattacharjee
    Kubernetes on Oracle OCI OKE : Quick Developer handouts3
    Topic posted July 13, 2019 by Joydeepta BhattacharjeeRed Ribbon: 250+ Points, tagged Containers, Docker, Kubernetes, Registry, Tip 
    Kubernetes on Oracle OCI OKE : Quick Developer handouts
    This would be constant effort to derive a ideal architecture and reference to derive a K8 MSA architecture with side car facilities like service mesh etc. for developers and architects to relate to Op

    In preparation of Oracle Cloud Infra based Micro-services platform with Kubernetes as a reference standpoint , trying to consolidate salient steps to built a resilient MS architecture. We can explore setting up Istio sidecar implementation as well with this for better governance and delivery but this tutorial would be more focused from developer angle hosting a consistent infrastructure to create development environment with 2 worker nodes of considerable size for hosting multiple containers. Below is a basic block diagram for creating a Kubernetes Infrastructure. To understand more on detail of Istio over OKE please refer the attached link

    The installation can also be done with clear articulated steps as per Helm Charts which helps to bundle and install almost all the required components.

    Now, based on the understanding of the current version of OKE provisioned we could architect a below reference diagram of Kubernetes over OCI stack. The OCI Image Registry would contained the build docker images of the app to be pulled into the Kubernetes PODs during runtime while bringing the containers up and running, On left the control plane has been shown with Master node showing up the api server, etcd database to store runtime information of pods and scheduler which are the internal components and have been incorporated as the Kubernetes release by community. On right hand side we have data plane to host application containers and services managed by Kubectl tool as the Worker nodes. We have provisioned only two worker nodes in OCI OKE with optimum sizing to host a minimal spring boot based micro service app. The default Ingress Load-balancer also shipped as part of Kubernetes. The API server inbuilt as part of Master Node architecture is responsible for routing the requests from outside the Kube cluster to the pods through the scheduler selected by the runtime on basis of present snapshot in etcd store.

    As a part of side car features there could be extra installation and configuration service mesh like Istio or monitoring tools like Prometheus and Grafana etc. These are all open source tools supported by Kubernetes community and provides lots of interesting features which also can be articulated in due time. Kubernetes has become a breakthrough inception for container orchestration with large set of features and capabilities and many vendors like Azure, Amazon, Oracle has started embracing and slowing maturing their stacks in a phenomenal diversification. Container orchestration has become very important in cloud fraternity to adapt to horizontal scaling, fault tolerance, automation and what more, The OCI native monitoring capability along with Kubernetes dashboard to configure metric and alters is also going in an interesting turn around to combine bare metal computation capability of vendor with global community driven Ops stack with many native options. IT is advisable to provision both the master and workers across multiple AD’s to give better availability and redundancy as well within a region for a Compartment assigned to the OCI account of customer. In fact as Oracle document quotes below “To ensure high availability, Container Engine for Kubernetes creates the Kubernetes Control Plane on multiple Oracle-managed master nodes (distributed across different availability domains in a region where supported).”

    Steps to Provisioning VM & configure workers and other basic installations:

    Document link from Oracle is pretty straight forward to create OCI OKE cluster

    Steps to Configure the OKE cluster:

    To create a cluster, you must either belong to the tenancy's Administrators group, or belong to a group to which a policy grants the CLUSTER_MANAGE permission.

    Once the cluster gets configured with all default setup we are now ready to create and deploy a service instance in the pod through the Master node of OCI OKE cluster. We can leverage Developer cloud services to build the code, create the docker image of the spring boot code from Job definition in CI-CD pipeline in Developer Cloud. Before that we would also create a deployment or pod definition configuration file in .yml which would finally been loaded approximately in a dockerized solution.

    Now lets go in detail to help creating the pods from the My-Services from a OCI Navigation in left and connect to the developer cloud services provisioned from console. The developer cloud services with current release has been a phenomenal to create a complete native pipeline to build both spring boot rest api and UI services , create images and then deploy in OKE clusters configured with it's cloud native Jobs configured. A typical JOB configured in the cloud native build pipeline has steps which can be configured from console for docker login, maven build , docker build and push image to Registry. I am not aware if Oracle still allows to integrate 3 rd party registry which is needed for interoperability between various cloud vendors.

    Once the image is built and pushed successfully versioned in the Image repository , the next step in the pipeline is to review the yaml in git for deployment and pod creation specific to Kubernetes shipped to specific Kubernetes vendor. The Kubernetes tooling has already been installed in Cloud VM in connection with master would now be utilized to sequentially create the pods with specific docker image runtime and provision in default inbuilt load balencer Ingress as part of Kubernetes setup . A typical docker image to build a spring boot api and create a pod and service to publish through Kubectl are sampled out as below. In developer cloud service under a typical project home all the artifacts and build jobs are organised so the specific user accessing devcs should have desired role for above visibility :

    Docker File in Spring boot Project context root, with a poc to update db store in Oracle Autonomous db cloud would be :

    FROM openjdk:8-jdk-alpine
    VOLUME /tmp
    ADD ./src/main/resources/Wallet_KXX /tmp/Wallet_KXX--- Wallet to securily connect the oracle db autonomous instance from a docker runtime
    COPY target/FirstPOCService-0.0.1-SNAPSHOT.jar app.jar
    ENTRYPOINT ["java","","-jar","/app.jar","--debug"]

    while the pod yaml to create a service type loadbalencer to register in OOTB Ingress with Kubernetes is as below .


    apiVersion: apps/v1beta1
    kind: Deployment
      name: app-dbboot-deployment
      replicas: 1
          app: app
            app: app
            - name: appdbtest
              image: ".............../firstspringpocdbimage:1.1"
         imagePullPolicy: "Always"
                - containerPort: 8099 #Endpoint is at port 80 in the container
              name: CCCC
    apiVersion: v1
    kind: Service
      name: springbootapp-db-service
      type: LoadBalancer #Exposes the service as a node port
      - port: 80
        protocol: TCP
        targetPort: 8099
        app: app

    Now , the typical steps to be executed ultimately to bring into life the pods as and that with the mighty Devcs automation is as below :

    echo "" >> $HOME/.oci/config
    echo "pass_phrase=bXXXX" >> $HOME/.oci/config
    cat $HOME/.oci/config
    mkdir -p $HOME/.kube
    oci ce cluster create-kubeconfig --cluster-id ocid.XXXXX--file $HOME/.kube/config --region eu-F>>>
    export KUBECONFIG=$HOME/.kube/config
    kubectl get pods
    kubectl config view
    kubectl get nodes
    kubectl delete service springbootapp-po-service
    kubectl delete deployment app-po-deployment
    kubectl create -f ./PO/po/springboot_db_deploy.yml
    sleep 60
    kubectl get services  springbootapp-po-service
    kubectl get pods

    This would be added as a Unix shell connected in built step and running below commands with kubectl . These are typical commands common to any K8 managed service by any cloud vendor and runs gracefully oracle as expected.


    Once this run successfully the Job logs under the specific build would list down the URL endpoint in the console itself and we dont need to really login to oci cli and bother with Black screen syndrome. I would also like to provide some experience around publishing a nginx container with angular app running on it in same way down the line so let's be on. Now those who are interested looking for further contribution and challenges you are facing to adopt this might K8 by Oracle stack. , meanwhile.

    Further , we have now used a Ingress-Nginx load balencer and using the service name which is created on deployment of the Pod could remove the dependency of communication between pods and services through IP . We would recommend to create pod deployment with service_type = cluster_ip and decouple it from OCI native load balencer. Rather , we would download an Nginx image as a reverse proxy in front in a pod and configure the routing rule to different backend pods from there. Optionally we can define a host in Ingress resource and edit /hosts/resolve.conf or update in Oracle public dns to expose it like I would like to preserve this blog link for all of us which can help in future