# Modifying docker opts no longer works
**URL:** https://travis-ci.community/t/modifying-docker-opts-no-longer-works/4715
**Category:** Linux
**Created:** [August 14, 2019, 8:49am UTC](https://travis-ci.community/t/modifying-docker-opts-no-longer-works/4715 "2019-08-14T08:49:22Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@stlaz](https://travis-ci.community/u/stlaz)
#### Post date: [August 14, 2019, 8:49am UTC](https://travis-ci.community/t/modifying-docker-opts-no-longer-works/4715/1 "2019-08-14T08:49:22Z")
Hey,
We’ve been modifying /etc/default/docker so that the daemon grabs the “–insecure-registry” option since our test environment requires it, but starting yesterday (or about that), this no longer seems to be propagated to the service.
Any idea why that would be?
See one of the builds failing: [https://travis-ci.com/openshift/oauth-proxy/builds/122994146](https://travis-ci.com/openshift/oauth-proxy/builds/122994146)
---
### Author:  [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)
#### Post date: [August 14, 2019, 12:44pm UTC](https://travis-ci.community/t/modifying-docker-opts-no-longer-works/4715/2 "2019-08-14T12:44:14Z")
We are moving the default Ubuntu release from Trusty to Xenial
> **[The Travis CI Blog: Ubuntu Xenial 16.04 as the default Travis CI build...](https://blog.travis-ci.com/2019-04-15-xenial-default-build-environment)**
>
> Xenial as the default Travis CI build environment is coming up next week, starting incrementally on Tuesday April 23rd, 2019.
>
> Since Ubuntu 14.04 reaches End of Life on April 30th, 2019, we’ll be g...
As a result, your build’s Docker version changed from [17.09.0-ce](https://travis-ci.com/openshift/oauth-proxy/builds/122824591#L35) to [18.06.0-ce](https://travis-ci.com/openshift/oauth-proxy/builds/122994146#L33). I suggest reviewing documentation to achieve the same effect.
---
### Author:  [@stlaz](https://travis-ci.community/u/stlaz)
#### Post date: [August 15, 2019, 12:02pm UTC](https://travis-ci.community/t/modifying-docker-opts-no-longer-works/4715/3 "2019-08-15T12:02:27Z")
Thanks,
Apparently the new version uses `/etc/docker/daemon.json` to configure the daemon.
Adding an example of how I fixed configuring insecure registries in our `before_script` section of `.travis.yml` in case other people encounter the same issue:
```auto
- "sudo cat /etc/docker/daemon.json | jq '. + {\"insecure-registries\": [\"172.30.0.0/16\"]}' | sudo tee /etc/docker/daemon.json"
```