Oracle® Cloud

Known Issues for Oracle Cloud Infrastructure Container Service Classic

E75879-15

May 2020

Known Issues for Oracle Cloud Infrastructure Container Service Classic

Learn about the issues you may encounter when using Oracle Cloud Infrastructure Container Service Classic and how to workaround them.

Note:

As of July 31, 2018 Oracle will no longer make any development improvements to Oracle Cloud Infrastructure Container Service Classic. This includes any future upgrades of the Docker Engine beyond the current version of v1.12.6 that is used in the cloud service.

For more information see My Oracle Support note 2423582.1

Topics:

Supported Browsers

Oracle Container Cloud Service supports the following the minimum requirements for web browsers:

Web Browser Version
Microsoft Internet Explorer 11 and later
Google Chrome 29 and later
Mozilla Firefox 24 and later
Apple Safari 9 and later

Deploying a Stack or Service Causes Oracle Cloud Infrastructure Container Service Classic to Hang If the Connection to the Docker Registry Is Lost

Issue: In certain circumstances, deploying a stack or service can cause Oracle Cloud Infrastructure Container Service Classic processes on the manager node to hang if a connection is lost from a worker node to the Docker registry when pulling a Docker image.

Workaround: To restart the Oracle Cloud Infrastructure Container Service Classic processes on the manager node:

  1. In a terminal window, login to the manager node using SSH.

  2. Type echo > /tmp/restart

    The Oracle Cloud Infrastructure Container Service Classic processes on the manager node are restarted. Worker nodes, and containers that are currently running on them, are not affected.

Some Docker Compose Version 2 Files Are Not Compatible with Oracle Cloud Infrastructure Container Service Classic

Issue: Certain Docker Compose version 2 files are not compatible with Oracle Cloud Infrastructure Container Service Classic. In particular, those docker-compose.yaml files that leverage newer Docker networking capabilities that work in conjunction with Docker Compose version 2.

Workaround: There is no workaround. Full Docker Compose version 2 support will be considered for a future release of Oracle Cloud Infrastructure Container Service Classic.

“Waiting on other phases” Message Might Be Displayed Unnecessarily

Issue: When deploying stacks that reference phased deployments (for example, the Wordpress Multihost example stack), a “Waiting on other phases” message might continue to show in the Oracle Cloud Infrastructure Container Service Classic Container Console UI for services in the deployment, even though all services have been deployed successfully.

Workaround: If all the services in the stack have been successfully deployed, ignore the message.

Misleading MANAGER_ADMIN_HOST and WORKER_ADMIN_HOST options in both the Source and the Destination Dropdown Lists in the Oracle Cloud Infrastructure Container Service Classic Console’s Create Access Rule Dialog

Issue: Having navigated to the Access Rules page from the Oracle Cloud Infrastructure Container Service Classic Console Services tab and clicked Create Rule, the Create Access Rule dialog is displayed. Both the Source dropdown list and the Destination dropdown list include four options:

  • MANAGER_ADMIN_HOST

  • MANAGER_MANAGER

  • WORKER_ADMIN_HOST

  • WORKER_WORKER

These options can be misleading when configuring Oracle Cloud Infrastructure Container Service Classic because:

  • Oracle Cloud Infrastructure Container Service Classic instances only ever have a single manager node. There’s no functional difference between MANAGER_ADMIN_HOST and MANAGER_MANAGER.

  • WORKER_ADMIN_HOST refers to the first host in the list of Oracle Cloud Infrastructure Container Service Classic worker nodes shown on the Service Details page. However, services and stacks can potentially be deployed on any worker node in the instance, according to the orchestration options specified for the deployment. Oracle Cloud Infrastructure Container Service Classic attaches no special significance to the first host in the list.

Furthermore, in a future release, the redundant MANAGER_ADMIN_HOST and WORKER_ADMIN_HOST options will be removed from both the Source and the Destination dropdown lists.

Workaround: To avoid confusion and unexpected behavior when specifying source and destination options for access rules:

  • To control access to or from the manager node, always create two access rules. Select the MANAGER_ADMIN_HOST option as the source or destination of one access rule, and the MANAGER_MANAGER option as the source or destination of the other rule.

  • To control access to or from worker nodes, always create two access rules. Select the WORKER_ADMIN_HOST option as the source or destination of one access rule, and the WORKER_WORKER option as the source or destination of the other rule. If you do want to specify a particular worker node as the source for an access rule, select <custom> and explicitly specify the worker node’s IP address.

Cannot Log in to Oracle Cloud Infrastructure Container Service Classic Container Console when Using Safari in Private Browsing Mode

Issue: If you attempt to log into the Container Console using the Safari browser in Private Browsing mode, you’ll get an ‘Invalid username or password’ error.

Workaround: Turn off Private Browsing in Safari and run it in normal mode. Alternatively, use a different browser in Private Browsing mode (for example, Chrome, Firefox, or Internet Explorer).

plus_ip and plus_suffix Template Functions Return Datatype Error if Passed .ServiceSlot as an Argument

Issue: The plus_ip and plus_suffix template functions return a datatype error if .ServiceSlot is passed as an argument.

Workaround: There is no workaround.

Webhooks Do Not Work As Expected

Issue: In some situations, calling a webhook created by Oracle Cloud Infrastructure Container Service Classic from a third party site (for example, Docker Hub) does not work as expected because Oracle Cloud Infrastructure Container Service Classic uses self-signed SSL certificates.

For example, you might specify a webhook for Docker Hub to call to trigger a re-deployment when it has re-built an application’s image after a change to the application's source code. In some situations, Docker Hub will not call the webhook successfully.

Workaround: If the third party system supports insecure SSL connections and transfers (for example, using a -k option), use this. Otherwise, add your own trusted SSL certificates to the Oracle Cloud Infrastructure Container Service Classic manager node.

Intermittent Problems When Scaling In or Scaling Out

Issue: Normally, you can scale out an Oracle Cloud Infrastructure Container Service Classic instance by adding worker nodes. Subsequently, you can scale in the Oracle Cloud Infrastructure Container Service Classic instance by removing the worker nodes that you’ve added. However, occasionally, you might be unable to add worker nodes, or remove worker nodes that you’ve previously added.

Workaround: Restart the Oracle Cloud Infrastructure Container Service Classic processes on the manager node:

  1. In a terminal window, login to the manager node using SSH.

  2. Type echo > /tmp/restart

    The Oracle Cloud Infrastructure Container Service Classic processes on the manager node are restarted. Worker nodes, and containers that are currently running on them, are not affected.

    You can now scale in and scale out worker nodes as required.

Worker Node Host’s Public IP Address No Longer Appears in Container Console

Issue: Normally, you can see the public IP addresses of worker node hosts on the Host Details page of the Oracle Cloud Infrastructure Container Service Classic Container Console. This makes it easy to copy the public IP address from the Host Details page. For example, if you want to verify that a deployed service is running. However, in some situations, after restarting the Oracle Cloud Infrastructure Container Service Classic processes on the manager node (for example, to add a new SSH key), worker node host public IP addresses are no longer shown on the Host Details page.

Workaround 1: Create a new service that returns a host’s public IP address, and deploy the new service on every host in the system as follows:

  1. On the Services page of the Container Console, click New Service to display the Service Editor.

  2. Enter updatepubip as the name for the new service.

  3. On the YAML tab, remove the default text, and copy and paste the following: 

    version: 2
services:
  updatepubip:
    image: 'oracle/oraclelinux:7.0'
    command: >-
      bash -c "mkdir -p /mnt/oracle; while true; do curl -s
      http://whatismyip.akamai.com/ -o /mnt/oracle/public_ip; sleep 20; done"
    volumes:
      - '/tmp/:/mnt'
    user: root
    environment:
      - 'occs:availability=per-host'

  4. Click Save to save the new service and close the Service Editor.

  5. On the Services page of the Container Console, click the Deploy button beside the updatepubip service that you just created and specify deployment options as follows:

    1. Keep the default of updatepubip as the name of the deployment

    2. Select a resource pool on which to deploy the service.

    3. Keep the defaults of 1 in the Quantity field, andper-host (on each host in this pool) in the list.

    4. Click Deploy.

  6. Repeat the previous step for every resource pool, until the updatepubip service has been deployed at least once on every host.

  7. Allow each deployment to run for at least a minute, and then stop and remove it as follows:

    1. On the Deployments page of the Container Console, click the Stop button beside the name of each running updatepubip deployment.

    2. When each deployment has stopped, either permanently remove the deployment from the host by clicking Remove, or simply retain the deployment in case you want to restart it later.

  8. On the Hosts page of the Container Console:

    1. Refresh the browser and notice that the pop-up list in the IP Addresses column beside each host name now contains the host’s public IP address.

    2. Click the name of the first host to display the Host Details page and refresh the browser. Notice that the public_ip address field now contains the host’s public IP address.

Workaround 2: (For systems with only a small number of hosts, you might find this workaround more appropriate than Workaround 1) Add a tag to each worker node host using the Oracle Cloud Infrastructure Container Service Classic Container Console, and specify the host’s public IP address as the tag’s name. You can then easily copy the public IP address from the Tags field on the Host Details page. If you don’t know the host’s public IP address, you can get it from the Service Details page of the Oracle Cloud Infrastructure Container Service Classic Console’s Services tab in the My Services application.

Only One SSH Key Can Be Active at Any One Time

Issue:You can add additional public SSH keys to Oracle Cloud Infrastructure Container Service Classic instances in your identity domain using the Oracle Cloud Infrastructure Container Service Classic Console (for example, if you lose the original private key or it gets corrupted).

Prior to Release 17.2.1, when you added a new public SSH key, the new key was appended to any existing public SSH keys in the /.ssh/authorized_keys file on the instance’s manager and worker nodes. Any existing public SSH keys could still be used. However, in subsequent releases, adding a new public SSH key replaces any existing public SSH keys.

Workaround: No workaround available.

Cannot Stop and Remove Deployments Because ‘Phantom Containers’ Are Running on Worker Node Hosts That Have Been Removed

Issue: In some situations, you cannot stop and remove deployments because Oracle Cloud Infrastructure Container Service Classic Container Console is showing containers running on non-existent hosts.

Having created an Oracle Cloud Infrastructure Container Service Classic instance with an initial number of worker node hosts, you can subsequently use the Service Console for Oracle Cloud Infrastructure Container Service Classic in the My Services application to add additional worker node hosts to improve system performance and resilience. Later on, you might decide you no longer need some or all of the additional hosts. In these situations, you can use the Service Console to scale in the instance to remove the additional hosts (note that you cannot remove the hosts that were initially created). If there’s a deployment (and its containers) running on a worker node host when you remove it, Oracle Cloud Infrastructure Container Service Classic:

  • stops and removes the running deployment and containers from the worker node host you’re about to remove

  • restarts the deployment and containers on the remaining hosts in the resource pool, according to the orchestration policy

  • removes the worker node host from the instance

However, where a deployment is running on the worker node host when you remove it, Oracle Cloud Infrastructure Container Service Classic Container Console incorrectly continues to show ‘phantom containers’ running on the now non-existent host. The ‘phantom containers’ are not actually running anywhere, and are not consuming any resource. But the fact that the ‘phantom containers’ are shown at all will prevent you subsequently stopping and removing the deployments for which they were originally created. That’s because Oracle Cloud Infrastructure Container Service Classic is unable to locate the ‘phantom containers’ to stop and remove them.

Workaround: Before attempting to remove a worker node host that you’ve previously added to an instance:

  1. In the Oracle Cloud Infrastructure Container Service Classic Container Console, create a new temporary resource pool and reassign to the new pool the worker node host you’re going to remove:

    1. On the Resource Pools page of the Container Console, click New Host Pool, enter details for the new resource pool, and click Save.

    2. Click Move Hosts and assign to the new resource pool the worker node host you’re going to remove.

      When you assign the worker node host to the new pool, any containers currently running on the host are stopped and restarted on the remaining hosts in the original resource pool (providing the remaining hosts comply with the original orchestration policy). As a result, the worker node host will have no containers running on it when you remove it.

  2. In the My Services application, use the Service Console for Oracle Cloud Infrastructure Container Service Classic to remove the worker node host:

    1. On the Services tab of the Service Console, click the name of the Oracle Cloud Infrastructure Container Service Classic instance from which you want to remove the worker node host.

    2. On the Service Overview page, expand the OCCS Worker Component region to see the worker node host in the Resources list.

    3. Click the Menu icon beside the worker node host that you want to remove, and select Remove Node.

  3. In the Oracle Cloud Infrastructure Container Service Classic Container Console, you’ll now be able to stop and remove deployments whenever you need to because no ‘phantom containers’ will be shown as running on non-existent hosts.

Removing worker node hosts that were initially specified when an instance was created is not only possible but also prevents additional worker node hosts being added later

Issue: When you create an Oracle Cloud Infrastructure Container Service Classic instance, you specify an initial number of worker node hosts. You can subsequently use the Service Console for Oracle Cloud Infrastructure Container Service Classic in the My Services application to add additional worker node hosts. Later on, you can remove some or all of the additional worker node hosts that you added. Expected behavior is that the Service Console prevents you from removing the worker node hosts that you initially specified.

However, in some situations, the Service Console does allow you to remove one or more of the initial worker node hosts. This is not intended behavior. Moreover, if you do remove one of the initial worker node hosts and then try to add additional worker node hosts, you'll be unable to do so.

Workaround: When creating an Oracle Cloud Infrastructure Container Service Classic instance, initially specify the minimum number of worker node hosts that the instance is ever likely to need. If you're not sure what that minimum number will be, initially create the instance with only one worker node host. Later on, you'll then be able to add and remove additional worker node hosts as necessary.

High Memory Compute Shapes Are No Longer Available for Worker Nodes

Issue: As of March 2017, high memory compute shapes are no longer selectable or available when defining worker nodes for Oracle Cloud Infrastructure Container Service Classic instances.

Workaround: There is no workaround.

Oracle Cloud Known Issues for Oracle Cloud Infrastructure Container Service Classic

E75879-15

Copyright © 2016, 2020, Oracle and/or its affiliates.

Primary Authors: Lisa Jamen, Jon Reeve, Mike Raab, Oracle Cloud Infrastructure Container Service Classic Development, Product Management, and QA teams

Describes issues and their workarounds for this release of Oracle Cloud Infrastructure Container Service Classic.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or “commercial computer software documentation” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

This document is intended for administrators who want to use Oracle Database Backup Service to back up Oracle databases to Oracle Cloud.

It is assumed you know the following:

  • Oracle Database concepts and basic database administration

  • Recovery Manager (RMAN) concepts, usage, tasks, and commands

  • The operating system environment under which you run Oracle Database

The following text conventions are used in this document:

Convention Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Accessible Access to Oracle Support

Oracle customers who have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

For more information, see these Oracle resources: