eugeneware / docker-wordpress-nginx

A Dockerfile that installs the latest wordpress, nginx and php-fpm.
MIT License
874 stars 380 forks source link

Step 8: Unmet dependencies #19

Closed tcn33 closed 10 years ago

tcn33 commented 10 years ago

Ubuntu Server 14.04 LTS running in a DigitalOcean droplet.

Step 8 : RUN apt-get -y install mysql-server mysql-client nginx php5-fpm php5-mysql php-apc pwgen python-setuptools curl git unzip
 ---> Running in 3137ce8cbfdc
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mysql-client : Depends: mysql-client-5.5 but it is not going to be installed
 mysql-server : Depends: mysql-server-5.5 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
2014/04/22 20:41:31 The command [/bin/sh -c apt-get -y install mysql-server mysql-client nginx php5-fpm php5-mysql php-apc pwgen python-setuptools curl git unzip] returned a non-zero code: 100
ajmorris commented 10 years ago

I've tired it a few times with various ubuntu flavors and am getting the same thing. I wonder if it's because when you install mysql-server, it jumps to an input screen and asks for a root password.

ghost commented 10 years ago

Same issue over here , Digitalocean droplet

The following packages have unmet dependencies: mysql-client : Depends: mysql-client-5.5 but it is not going to be installed mysql-server : Depends: mysql-server-5.5 but it is not going to be installed

ghost commented 10 years ago

SOLVED: Just: docker pull jbfink/docker-wordpress and he'll install all the dependencies https://index.docker.io/u/jbfink/docker-wordpress/

you can also use: https://index.docker.io/u/tutum/wordpress/

AsavarTzeth commented 10 years ago

No, not solved... Pulling jbfink/docker-wordpress or building it manually makes no difference.

Also, I may be a docker newbie, but I am not even sure that makes sense.

ghost commented 10 years ago

Worked for me , I just pulled with the command and he installed all the dependencies alone .

AsavarTzeth commented 10 years ago

Also, I may be a docker newbie, but I am not even sure that makes sense. I am quite confident the issue is that Ubuntu 14.04 (which I assume you run as well) is using mysql 5.6 and not 5.5, making the scripts fail. I also assume that since 14.04 is relative new they simply have not updated it yet.

EDIT: Yes I re-read and see the poster is indeed running 14.04 like me. Of course it fails trying to install mysql 5.5...

ajmorris commented 10 years ago

@haperlot jbfink/docker-wordpress is LAMP, not LEMP (meaning it uses Apache instead of Nginx). So that doesn't make sense.

Instead what needs to be done is someone needs to update the Dockerfile in this repo to fix the dependencies issue.

One way of doing that is comparing the Dockerfile proposed "solution" in this thread to the Dockerfile in this repo and updating it to see if the dependencies are fixed. Hopefully I'll have some time to look at the differences this afternoon.

@AsavarTzeth it's not a newbie thing. They are entirely different repos. The Docker containers created are different. While the one works (jbfind/docker-wordpress), it uses Apache as the HTTPD server instead of nginx, which is what this repo does. I'll see what I can do to offer a PR for this issue in the next day or so.

AsavarTzeth commented 10 years ago

What I don't get is why a meta-package like mysql-server and msql-client fails. Should it not simply get the latest version and be done with it? The build acts just as if it tried apt-get -y install mysql-server-5.5 but it should not.

Edit: Nvm I see the container is based on an earlier Ubuntu without access to 5.6. I realize this is not something I can comprehend at the moment. :)

tcn33 commented 10 years ago

I've forked the repo here and updated it to use trusty rather than precise. This resolves the dependencies issue but then creates a whole set of other ones as the default location for nginx in 14.04 is /usr/share/nginx/html rather than /usr/share/nginx/www. I've cleaned all of those up in the Dockerfile, start.sh and nginx-site.conf but I now just get an nginx 404 page for WP. Hopefully someone with a bit more nginx experience can work out why.

eugeneware commented 10 years ago

Hi Guys, sorry - I've been away due to some personal circumstances. I'll take a look into this once I get a chance. Happy to take a look at any PRs in the meantime though!

It worked fine on Ubuntu 12.x, looks like a 14.x issue.

On Tue, Apr 29, 2014 at 6:53 AM, tcn33 notifications@github.com wrote:

I've forked the repo herehttps://github.com/tcn33/docker-wordpress-nginx/commit/9ff2625ca1bf34fbd92e3874a0833ec99cdc1beband updated the repo it uses to trusty. This resolves the dependencies issue but then creates a whole set of other ones as the default location for nginx is /usr/share/nginx/html rather than /usr/share/nginx/www. I've cleaned all of those up in the Dockerfile, start.sh and nginx-site.conf but I now just get an nginx 404 page for WP. Hopefully someone with a bit more nginx experience can work out why.

— Reply to this email directly or view it on GitHubhttps://github.com/eugeneware/docker-wordpress-nginx/issues/19#issuecomment-41612093 .

Eugene Ware Chief Executive Officer

Phone: +61 3 9955 7041 Email: eugene@noblesamurai.com Twitter: @EugeneWare http://twitter.com/EugeneWare

Noble Samurai Pty Ltd Level 1, 234 Whitehorse Rd Nunawading, Victoria, 3131, Australia

noblesamurai.com http://www.noblesamurai.com/ | eugeneware.com | facebook.com/Eugene.S.Ware http://www.facebook.com/Eugene.S.Ware

joelchen commented 10 years ago

Hi all,

I have fixed this issue in the latest Pull Request [https://github.com/eugeneware/docker-wordpress-nginx/pull/20].

Warmest Regards, Joel

eugeneware commented 10 years ago

Should be fixed in #20. Thanks @joelchen