-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coach create doesn't work, can't find images #9
Comments
While going back, commit 27254d8 seems to work |
are you saying that if you bisect, this commit is the last working commit? |
The "missing image" should be pretty easy for me to investigate, so I will do it now. Please note 2 things:
|
I'm investigating this now |
this issue could come from images that are not using the "latest" tag. Maybe I've missed something about passing image tags into the create process. I'll take a look there. |
I most certainly made a mistake related to image tags. I am fixing it now. Note that I am checking some other operations that might also have issues now: pull, build, destroy |
@aleksijohansson #12 should fix issues related to images with tags in build, create, destroy, pull operations. |
PR merged. |
Tried with the latest version of coach from master. Same issue, different error. Please see screenshot: https://goo.gl/photos/Q72wymvanjV4B1nr8 Go 1.4.2 Also another issue after the tag changes in docker pull. Filing another issue for that. |
I can't recreate that image tag issue with the latest master. Right now the only issue is the following: (Fedora 22)
This is a docker error message, which says that the image has no CMD entry in the Dockerfile. The only case where an image is legal without a CMD entry is if using the run operation. I will remove pulled images and try it again. |
@aleksijohansson confirmed that I cannot recreate the image tag issue, after removing all images and starting from scratch. I can perform that pull, build and create options, and am only blocked by missing CMDs in the php and nginx images. I will now investigate the images themselves to see if the docker client is confused about the missing CMDs. |
the "no command specified" issue is being caused by poor code in the create operation which is not properly identifying the image. I am working on fixing that now. |
This PR should fix the "no command specified" which seemed to occur in all build cases (as opposed to pull cases) |
Tested on Fedora, RancherOS and CoreOS and seems to be working really good now! Whole workflow: coach init git https://github.com/aleksijohansson/docker-drupal-coach Fedora 22: Go: Docker: Client: Server: RancherOS: Go: Docker: CoreOS: Go: Docker: |
coach create can't find images, even though they are there.
Tested with:
https://github.com/aleksijohansson/docker-drupal-coach
Tested on:
RancherOS, Docker 1.7.1
CoreOS, Docker 1.6.2
Error output:
core@pur ~/Sites/test/docker-drupal-coach $ coach create
(5)[OPERATION][CREATE]------ running create operation
(3)[NODES][NODE:memcache]--- ERROR FAILED TO CREATE INSTANCE CONTAINER [drupal_memcache_single FROM memcached] =>no such image
(3)[NODES][NODE:mariadb]---- ERROR FAILED TO CREATE INSTANCE CONTAINER [drupal_mariadb_single FROM mariadb] =>no such image
(3)[NODES][NODE:php]-------- ERROR FAILED TO CREATE INSTANCE CONTAINER [drupal_php_single FROM aleksijohansson/drupal-php-fpm] =>no such image
(3)[NODES][NODE:nginx]------ ERROR FAILED TO CREATE INSTANCE CONTAINER [drupal_nginx_single FROM drupal_nginx] =>API error (500): Could not get container for drupal_php_single
The text was updated successfully, but these errors were encountered: