Docker Community Forums

Share and learn in the Docker community.

Docker RC Beta 18 runtime errors


(V9chris) #1

Expected behavior

Running docker-compose just works (as it did pre 18)

Actual behavior

After upgrading to beta 18 and running docker-compose up I get the following errors

ERROR: for mongodb Unknown runtime specified default
ERROR: for redis Unknown runtime specified default
ERROR: for rabbitmq Unknown runtime specified default

Information

Docker for Mac: version: mac-v1.12.0-beta18-3-gec40b14
OS X: version 10.10.5 (build: 14F27)
logs: /tmp/20160706-130036.tar.gz
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Here is my redis dockerfile for reference…

FROM redis:3.2.0
CMD [“redis-server”]
EXPOSE 6379

and in my docker-compose file

redis:
build: ./redis/.
ports:
- 6379:6379


(Guillaume Cauchon) #2

Why are you building your own images instead of using the official ones available on hub.docker.com? There already are images for different versions of Mongo, Redis and RabbitMQ

Your docler-compose.yml would look like this, without the build config:

redis:
    image: redis:3.2
mongodb:
    image: mongo:latest
...

I have a similar setup on a local projet I use daily and it still work with beta18


(John Pape) #3

“Why are you building your own images instead of using the official ones available on hub.docker.com?”

There are so many things wrong with that statement. Who cares if he’s building his own containers, that’s what docker build was created to do…

FWIW - I have the same issue as the OP… I can’t start a node.js development container I was using fine yesterday. Nor can I start a uifd/ui-for-docker container that was running just fine until I upgraded…


(V9chris) #4

Thanks John,

I have managed to fix my issue for the time being with the following process, not sure if it will help you.

Quit and Resart docker
Then in terminal I ran the following cleanup commands;

docker stop $(docker ps -aq) This stops all containers
docker rm $(docker ps -aq) This will remove all containers
docker rmi $(docker images -aq) This will remove all images
docker volume rm $(docker volume ls -q) This will remove all volumes

Less than ideal because it takes me a long time to rebuild my project - it’s quite large.
At least It’s working for now. :sweat_smile:


(Guillaume Cauchon) #5

How can a question be wrong?

Look at the image definition above… I’m sorry but it is useless to define/build your own image it there is nothing custom in it. Call me stupid for not wanting to reinvent the wheel!

If you are to comment on an issue, it better be relevant…

I happen to still have the beta17 .dmg so I downgraded, cleared all my images and containers and ran a test to post valuable information to document the issue.

docker-compose.yml

version: '2'
services:
  redis:
    image: redis:3.0
  node:
    image: node
    links:
      - redis

beta17

Docker for Mac: version: mac-v1.12.0-beta17
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160706-102039.tar.gz
[OK]     docker-cli
[OK]     app
[OK]     menubar
[OK]     virtualization
[OK]     system
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

:chart_with_upwards_trend: both containers are starting fine.

beta18

Docker for Mac: version: mac-v1.12.0-beta18-3-gec40b14
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160706-102530.tar.gz
[OK]     docker-cli
[OK]     app
[OK]     menubar
[OK]     virtualization
[OK]     system
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

:boom:

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

Workaround

docker-compose up --force-recreate

:chart_with_upwards_trend: both containers are starting fine.


There are so many things wrong with that statement.

Says who?


(John Pape) #6

Glad to hear it.

Stay relevant, my friends.


(Hijinkies) #7

Look at the image definition above… I’m sorry but it is useless to define/build your own image it there is nothing custom in it. Call me stupid for not wanting to reinvent the wheel!

Since we are only supposed to criticize ideas instead of people … I think your idea is stupid and infantile for many reasons. We can have an offline discussion why because …

If you are to comment on an issue, it better be relevant…

I too am experiencing this issue with beta18 when attempting to restart the stock mongo from hub.

Docker for Mac: version: mac-v1.12.0-beta18-3-gec40b14
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160706-163902.tar.gz
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

~ » docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c01bbe09fa38 mquandalle/wekan "/bin/sh -c 'bash $ME" 5 days ago Exited (0) 25 hours ago 0.0.0.0:8081->80/tcp agitated_darwin e9b40be7df93 mongo "/entrypoint.sh mongo" 6 days ago Exited (0) 4 days ago wekan-mongodb ~ » docker start e9b40be7df93 -a -i Error response from daemon: Unknown runtime specified default

I’ve got data in my mongo instance that I want to save, so I’m disinclined to just blow the entire volume away and make it again.


(Guillaume Cauchon) #8

I’ve got data in my mongo instance that I want to save, so I’m disinclined to just blow the entire volume away and make it again

Is the data in the container or a separate data volume container?

I assume the first since you don’t want to lose it… Then I guess your only solution is to downgrade to beta17.

If not, you can rebuild only the service container with docker-compose build mongo (assuming your mongo service alias is “mongo”)