DC/OS 1.10 Beta 1

DownloadView Documentation →

DC/OS 1.10.0 Beta 1

This beta release is for testing only and not to be used in production. It will only support new installations.

DC/OS 1.10.0 Beta 1 has a number of limitations that will be resolved at GA time:

  • Upgrades from 1.9 are not supported.
  • DC/OS 1.10 requires CLI version 0.5.3.
    • Uninstall the existing CLI.
    • Install version 0.5.3 using the Install CLI instructions in the dropdown in the upper left hand corner of the 1.10 DC/OS GUI.
    Note: CLI version 0.5.3 is not compatible with DC/OS 1.9.
  • If you cannot access Marathon and you see the trustAnchors parameter must be non-empty in the logs, restart Marathon. Restart Marathon by entering the following command on the master node with the leading Marathon master: sudo systemctl restart dcos-marathon.service.
Please try out the new features and updated data services. Provide any feedback through Jira: https://jira.dcos.io.

DC/OS 1.10 includes many new capabilities for Operators and expands the collection of Data & Developer Services with a focus on:

  • Core DC/OS Service Continuity - System resilience, cluster and node checks, UCR and Pods improvements.
  • CNI Networking enhancements for broader networking support.
  • Data Services enhancements.


New Features and Capabilities

Apache Mesos 1.4 and Marathon 1.5 Integrated.

  • DC/OS 1.10 is is based on Mesos 1.4.0, here using master branch (pre-release) SHA 013f7e21, with over 1200 commits since the previous Mesos version. View the changelog.

  • DC/OS 1.10 is integrated with the latest release of Marathon, version 1.5. Resulting breaking changes and new features are documented below. For more information about Marathon 1.5, consult the Marathon changelog.


  • Configurable Spartan upstreams for domains (dnames). You can now configure Spartan to delegate a particular domain (e.g. "*.foo.company.com") to a particular upstream.

  • Increased CNI network support. DC/OS now supports any type of CNI network. View the documentation.


  • Node and Cluster health checks. Write your own custom health checks or use the predefined checks to access and use information about your cluster, including available ports, Mesos agent status, and IP detect script validation. View the documentation.
  • Enhanced upgrades with pre/post flight checks.
  • UCR.
  • Scale and performance limits.



The GUI sidebar tabs have been updated to offer a more intuitive experience.

  • The "Deployments" subpage under the "Services" tab has been moved to a toggle-able modal in the "Services" page.
  • The "Security" tab has been removed. The "Secrets" tab that used to be under "Security" is now a top-level tab.
  • The "Universe" tab has been renamed to "Catalog" and the "Installed" subpage has been removed.
  • The "System Overview" tab has been renamed to "Overview".

Updated DC/OS Data Services

  • Rolling Configuration Update and Upgrades support via CLI.
  • Ability to deploy Data Services into Folders to enable multi team deployments.
  • Ability to deploy to CNI-Based Virtual Networks.

The following updated data services packages are also in beta and are compatible with DC/OS 1.10.

Breaking Changes

  • Upgrades not supported in 1.10.0 Beta 1. Upgrades from 1.9 to 1.10 are not supported in 1.10.0 Beta 1. Upgrades will be supported in a future 1.10 release.

  • Marathon Networking API Changes in 1.5 The networking section of the Marathon API has changed significantly in version 1.5. Marathon can still accept requests using the 1.4 version of the API, but it will always reply with the 1.5 version of the app definition. This will break tools that consume networking-related fields of the service definition. View the documentation.

  • REX-Ray configuration change DC/OS 1.10 upgrades REX-Ray from v03.3. to v0.9.0 and therefore the REX-Ray configuration format has changed. If you have specified custom REX-Ray configuration in the REX-Ray_config parameter of your config.yaml file, change the parameter to REX-Ray_config_preset: aws.

  • New flow to change the dcos_url and login The new command to change your cluster URL is dcos cluster setup <dcos_url>. This change will break any existing tooling that uses the former command. Backwards compatibility is slated for a future patch release.

Known Issues and Limitations

  • DCOS-9444 - Task Remaining on Marathon 15.7 from guano backup.
  • DCOS-13762 - SDK Integration with DC/OS Folders.
  • DCOS-14534 - Marathon: Verbose Server Banner.
  • DCOS-14535 - Marathon GUI: Error Messages are Too Verbose.
  • DCOS-14536 - UI Vulnerable to Clickjacking (aka UI Redressing).
  • DCOS-15284 - Marathon Task Stuck.
  • DCOS-16547 - Task state does not update after the agent running it was removed from the cluster.
  • DCOS-16564 - UI error message references Marathon command.
  • DCOS-17294 - Unable to curl (resolve) applications using Mesos DNS names.
  • DCOS-17321 - Fix upgrade of Marathon-lb from 1.9-1.10.
  • DCOS-17502 - AdminRouter rejecting request to install package.
  • DCOS_OSS-1340 - Spartan "autoip" DNS should resolve to host IP for UCR in bridge network.
  • DCOS_OSS-1486 - Metrics agent crashes when the mesos containers endpoint is missing fields.
  • INFINITY-1143 - Update / Uninstall. DSE does not support rolling upgrade.
  • INFINITY-1809 - [Data Svc] DC/OS Service Update / Config Update / Maintenance.
  • INFINITY-2054 - Extend --replace={true|false} for CLI.
  • MESOS-6950 - Launching two tasks with the same Docker image simultaneously may cause a staging dir never cleaned up.
  • MARATHON-7654 - Marathon cannot replace persistent tasks for rebooted hosts until the Mesos Master forgets about the old agent.

Major Issues Fixed since 1.9

  • DCOS-10873 - Marathon - Groups (and apps) endpoints return deprecated field.
  • DCOS-10928 - Marathon leader election fails after OS upgrade.
  • DCOS-11242 - Rounding issue with memory UI.
  • DCOS-12154 - Minuteman: Failed to parse task.
  • DCOS-13595 - Incomplete uninstall of package kafka due to Mesos unavailability.
  • DCOS-14644 - Cannot use systemd socket for pkgpanda API.
  • DCOS-14852 - Cosmos - Installed packages tab not functioning.
  • DCOS-14872 - Filesystem corruption in dcos-ui container.
  • DCOS-14886 - Updated the internal diagnostics utility (dcos-3dt.service).
  • DCOS-15044 - Metrics API returning null value for datapoint for Cassandra service.
  • DCOS-15232 - DC/OS Services UI does not expose the Service ports for a service.
  • DCOS-15302 - Pkgpanda redirects stderr to stdout.
  • DCOS-15307 - Cannot "dcos task exec" to tasks in pods.
  • DCOS-15247 - Spartan repeatedly crashing on some nodes.
  • DCOS-15332 - DC/OS login prompt vulnerability.
  • DCOS-15590 - DCOS cli confirm() is not non-interactive safe.
  • DCOS-15653 - Excessive log rotation for Mesos logs.
  • DCOS-15914 - Support for CentOS/RHEL 7.4 with 1.9.
  • DCOS-15937 - Pods do not receive SIGTERM.
  • DCOS-16151 - Marathon Endpoints are not responding.
  • DCOS-16588 - In 1.9, the Mesos-DNS component by default did not set the truncate bit in responses. This is non-conforming behavior. The new default in 1.10 will be to set the truncate bit if the response is too large to fit in a single packet and therefore gets truncated. If you do not want TCP retry, set mesos_dns_set_truncate_bit to false in your config.yaml file at install time. The default is true.
  • DCOS-16725 - Marathon /ping Response Headers Changes on DC/OS 1.8.7 to 1.9.
  • DCOS_OSS-839 - Upgrade script fails silently.
  • DCOS_OSS-902 - Minuteman code in separate repo from navstar.
  • DCOS_OSS-980 - Docker 1.12 and later breaks virtual networks.
  • MESOS-5187 - The filesystem/linux isolator does not set the permissions of the host_path.
  • MESOS-7057 - Consider using the relink functionality of libprocess in the executor driver.
  • MESOS-7830 - Sandbox_path volume does not have ownership set correctly.
  • PR 1395 - Add HTTP routing for Azure templates.
  • Updated dcos-launch, now includes user's guide.