# Upgrading the underlying operating system for the Docker executor **URL:** \ **Category:** Announcements\ **Tags:** docker\ **Created:** [March 15, 2019, 4:32pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030 "2019-03-15T16:32:35Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![alexey](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alexey/32/42_2.png) [@alexey](https://discuss.circleci.com/u/alexey)\ **Post date:** [March 15, 2019, 4:32pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/1 "2019-03-15T16:32:35Z")
We are upgrading the version of the operating system that we use to run customer containers as part of the Docker executor on CircleCI. This change should be mostly invisible to you, but you might notice this change if you are, for example, relying on a specific kernel version in your jobs. We are slowly rolling out this change for all Docker executor customers, and we expect the rollout to be complete by April 1st, 2019. Here are the facts: - A small portion of the Docker executor jobs are now executing on the machines with the upgraded OS. We will increase that portion slowly over the coming weeks. - Most of the underlying OS changes will not be visible to the Docker executor jobs, as those are isolated in their own containers. However, the upgrade includes a new kernel version which will be visible. - Some kernel-specific or OS-specific changes to data structures exported in virtual filesystems (such as `/proc/self/cgroup`) will be visible in the Docker executor jobs. - The new version of the kernel is GNU/Linux 4.15. - The Docker version in the Docker executor is being upgraded from `17.05` to `18.09`. Please comment on this post if you have any questions about this change. Thank you! ---
**Author:** ![katelynsills](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/katelynsills/32/21616_2.png) [@katelynsills](https://discuss.circleci.com/u/katelynsills)\ **Post date:** [March 18, 2019, 11:57pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/2 "2019-03-18T23:57:08Z")
We’ve been getting continuous repeated errors on previously passing tests since Friday March 15. The tests are using the docker image `circleci/node:11-browsers` and using `puppeteer-core` to run the browser tests. I’m curious if our issues ([bug report here](https://discuss.circleci.com/t/navigation-failed-because-browser-has-disconnected/29087)) might be related to this upgrade, since both started to happen around the same time. ---
**Author:** ![alexey](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alexey/32/42_2.png) [@alexey](https://discuss.circleci.com/u/alexey)\ **Post date:** [March 19, 2019, 1:47pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/3 "2019-03-19T13:47:15Z")
Hi Kate, thanks for reporting this. We’ll investigate and update this thread and your bug report with more information. Thanks for your patience. ---
**Author:** ![alexey](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alexey/32/42_2.png) [@alexey](https://discuss.circleci.com/u/alexey)\ **Post date:** [March 19, 2019, 2:01pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/4 "2019-03-19T14:01:42Z")
We have identified a possible cause of this issue. We won’t run any jobs on the upgraded OS before the fix is out. So your affected jobs should now work fine again. We’ll update here once the fix is rolled out. Thanks for your patience. ---
**Author:** ![ego](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ego/32/31011_2.png) [@ego](https://discuss.circleci.com/u/ego)\ **Post date:** [March 21, 2019, 12:58pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/5 "2019-03-21T12:58:33Z")
Our builds have started failing today, were passing yesterday we use ```auto machine: image: circleci/classic:latest ``` could this be the reason? ---
**Author:** ![ego](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ego/32/31011_2.png) [@ego](https://discuss.circleci.com/u/ego)\ **Post date:** [March 21, 2019, 12:59pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/6 "2019-03-21T12:59:32Z")
also… where can I find a list of available tags for the `circleci/classic` image? so I can try something other than `latest` ---
**Author:** ![ego](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ego/32/31011_2.png) [@ego](https://discuss.circleci.com/u/ego)\ **Post date:** [March 21, 2019, 1:11pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/7 "2019-03-21T13:11:49Z")
the only list of `classic` tags I could find is here: [https://circleci.com/docs/2.0/configuration-reference/#machine](https://circleci.com/docs/2.0/configuration-reference/#machine) is this up to date? if a new version was released today shouldn’t it be on that list? ---
**Author:** ![glenjamin.circleci](https://avatars.discourse-cdn.com/v4/letter/g/73ab20/32.png) [@glenjamin.circleci](https://discuss.circleci.com/u/glenjamin.circleci)\ **Post date:** [March 21, 2019, 2:20pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/8 "2019-03-21T14:20:33Z")
These changes we’re making will only affect people using the `docker` executor type. ---
**Author:** ![glenjamin.circleci](https://avatars.discourse-cdn.com/v4/letter/g/73ab20/32.png) [@glenjamin.circleci](https://discuss.circleci.com/u/glenjamin.circleci)\ **Post date:** [March 25, 2019, 3:08pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/9 "2019-03-25T15:08:23Z")
We had disabled the new image for a few days after reports of issues running Chrome in containers hitting security errors. We have resolved those issues and are now continuing our rollout. ---
**Author:** ![yoyoyoyo](https://avatars.discourse-cdn.com/v4/letter/y/6bbea6/32.png) [@yoyoyoyo](https://discuss.circleci.com/u/yoyoyoyo)\ **Post date:** [March 25, 2019, 4:10pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/10 "2019-03-25T16:10:40Z")
I’m seeing some new and unexpected errors using the `circleci/elixir:1.7.3-node-browsers` image. Is there any way for me to check which executor version I’m on to see if `18.09` is breaking my build or not? ---
**Author:** ![drazisil](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/drazisil/32/24029_2.png) [@drazisil](https://discuss.circleci.com/u/drazisil)\ **Post date:** [March 25, 2019, 4:17pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/11 "2019-03-25T16:17:35Z")
I’ll defer to Glen, but you could add a step that runs `lsb_release -a` to check what version of linux you are on. ---
**Author:** ![yoyoyoyo](https://avatars.discourse-cdn.com/v4/letter/y/6bbea6/32.png) [@yoyoyoyo](https://discuss.circleci.com/u/yoyoyoyo)\ **Post date:** [March 25, 2019, 5:43pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/12 "2019-03-25T17:43:27Z")
@drazisil 'm not familiar with this command. Is that something on the elixir image? ---
**Author:** ![drazisil](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/drazisil/32/24029_2.png) [@drazisil](https://discuss.circleci.com/u/drazisil)\ **Post date:** [March 25, 2019, 5:51pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/13 "2019-03-25T17:51:12Z")
It’s a debian/ubuntu command. It does work under the docker executor through. Edit: To address your confusion, this is about the machine executor. If you are using the docker executor this would not affect you. ---
**Author:** ![jkzilla](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jkzilla/32/19750_2.png) [@jkzilla](https://discuss.circleci.com/u/jkzilla)\ **Post date:** [April 2, 2019, 5:46pm UTC](https://discuss.circleci.com/t/upgrading-the-underlying-operating-system-for-the-docker-executor/29030/14 "2019-04-02T17:46:05Z")
**Update:** The version upgrade of the operating system is currently under review, with security reviews slated to be completed over the coming weeks. This version of the operating system runs on customer containers as part of the _ **Docker executor** _ on CircleCI. Please note - this change should be mostly invisible to you, but you might notice this change if you are, for example, relying on a specific kernel version in your jobs.