Docker Community Forums

Share and learn in the Docker community.

Unknown runtime specified default


(Jeshuaborges) #1

Expected behavior

When using docker compose I expect that linked services start.

Actual behavior

After updating to the latest docker for mac I am now unable to run any docker compose services. I receive an error message “Unknown runtime specified default” for every dependent service.

$ docker-compose up
Starting pegasusbeta_db_1
Starting pegasusbeta_elasticsearch_1

ERROR: for elasticsearch  Unknown runtime specified default

ERROR: for db  Unknown runtime specified default
ERROR: Encountered errors while bringing up the project.


My docker-compose.yml

  build: .
    - DATABASE_URL=mysql2://root@db:3306
    - ELASTICSEARCH_URL=http://elasticsearch:9200
    - .env
    - .:/app
    - "3000:3000"
    - "35729:35729"
    - db
    - elasticsearch

  image: mysql:5.6
    - "3306:3306"

  image: elasticsearch:1.5.2
  • Docker for Mac: version: mac-v1.12.0-beta18
  • OS X: version 10.11.5 (build: 15F34)

Diagnostic ID: 347260B9-59B5-4A4E-89CA-F1F074EA64CF

Unable to relaunch container after update 1.12.0-rc3-beta18
(Blake) #2

I am experiencing this same problem immediately after updating to the latest version.

(Alberthild) #3

same here, after update to the newest version…

(Jonathan Brinley) #4

Looks related to Removing the containers and restarting them partially resolves the issue. The containers will start, but logging doesn’t work. “jack is incompatible with use of CloseNotifier in same ServeHTTP call”

(Gustavostor) #5

Same here. A quick solution that worked for me is to “Reset to factory settings” on Docker preferences. Since I use Docker for Mac only for development, I don’t care about losing volume data.

(Thepixeldeveloper) #6


Don’t update to this version if you can help it.

(Gustavostor) #7

Is there any way to downgrade?

(Eric Rutherford) #8

Deleting my containers and re-upping fixed it for me. I should note that I also nuked my volumes associated to the containers that wouldn’t start…

Looking at the containers that wouldn’t start it was probably related to the volumes since the only ones that wouldn’t start were the ones with volume* mounts.

(Alberthild) #9

is there a way to change the runtime for a container?

$ docker inspect postgres |grep runtime
"runtime": “default”,

on a new created container its “runc”:

$ docker inspect modest_jennings |grep runtime
"runtime": “runc”,

(Sandrodz) #10

yes it seems to happen to everyone. reseting to factory defaults fixes it.

(Aaron Eikenberry) #11

Is there a workaround for this http: Hijack is incompatible with use of CloseNotifier in same ServeHTTP call issue? I’m able to start containers, but am unable to run commands such as: docker-compose run django python createsuperuser and since all my data was wiped in this upgrade, it’s hard to get anywhere.

(Gustavostor) #12

I think you’re running the command, but you’re not seeing any logs. What I did here was after I ran docker-compose up, I attached to each container which I care about the logs individually

(Aaron Eikenberry) #13

I tried answering the prompts that should be visible, but no dice. I ended up downgrading to the previous version and I’m back in business. Thanks though!

(Alecoletti) #14

I’m having the same problem with the last update: 1.12.0-rc3-beta18 (build: 9969) Any idea on how to downgrade?

(Docker4gk) #15

I was able to restore previous version from trash. Removed and recreated the containers. It works now.
Downgrade link.

(Mikemitterer) #16

Phuu - you save my day. Thanks! I stopped Docker. Reinstalled it from your .dmg - everything is back to normal again.

(Chris Jones) #17

Downgrading worked. It also looks like the update has been pulled as version 1.12.0-rc2-beta17 (build: 9779) is now telling me I have the most recent version.

(Giginos) #18

Try: docker-compose up --force-recreate