Closed activedecay closed 7 years ago
Should work as expected I'll double check
Please provide your steps :)
good deal!
i have a vagrant box using a ceph/ubuntu-xenial basebox
# vagrant init ceph/ubuntu-xenial
# vagrant up
# vagrant ssh
the prompt is now vagrant@thebox:~$
do the needful
git clone https://github.com/openmeetings/openmeetings-docker.git
cd openmeetings-docker
nohup docker build . &
a link to nohup.out https://drive.google.com/file/d/0B-Yoemv8xz62RF9GNTVOOHRWeWs/view?usp=sharing
please check the link for output
Will try to check the script(s) tonight, seems MySql server was updated and have to be installed differently Maybe will switch to PostgeSql
Should work now, please check
i dunno, but seems like the same failure https://drive.google.com/file/d/0BwKUTsk23OzZRnpwNHpJN2o4U3M/view?usp=sharing
hmm, you have
* Starting MySQL database server mysqld
...fail!
in your logs .... not sure why, will try to reproduce
Can you start thr Docker and try to start MySql manually? What would be the error?
after messing around, I finally figured out what __HASH__
means. it's the IMAGE ID found when executing docker image ls
-- and it's the one without a repository, i guess...
This shows up in the mysql error log
2017-10-16T15:34:33.731594Z 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table storage engine for 'proxies_priv' doesn't have this option
2017-10-16T15:34:33.731679Z 0 [ERROR] Aborting
full context: https://hastebin.com/dewitiyuwu.pl
https://serverfault.com/a/872576/398062 is this the solution? the stackoverflow question is nearly identical to my experience.
Sorry, don't have much time to test right now :((( You can login to docker image as described in README:
docker run -it __HASH__
i've been editing my comments, please see above. the sql error and the stackoverflow solution don't seem to work. thanks for your time, no rush
Hello, just performed clean install using:
docker rmi -f $(docker images -a -q)
docker build .
docker run -it __HASH__
all good :(( Docker: latest under Ubuntu 17.04 Maybe you are performing any additional steps?
I'll try under 17.04 I've been using 16.04 🌶️
should be the same, will try using 16.04 later this week Docker image is based on 16.04 .... something weird :(
Checking on 16.04 ... Oracle java8 fails to be downloaded, will double-check tomorrow and will replace with openjdk ...
Nice catch!
On Oct 17, 2017 8:40 PM, "Maxim Solodovnik" notifications@github.com wrote:
Checking on 16.04 ... Oracle java8 fails to be downloaded, will double-check tomorrow and will replace with openjdk ...
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openmeetings/openmeetings-docker/issues/2#issuecomment-337443815, or mute the thread https://github.com/notifications/unsubscribe-auth/AEGWlvF3OUR7ks9YeMG8uBYXXeq9gdbSks5stWU3gaJpZM4PoItE .
Will also try to build and publish image, so it will be available without re-building
Please try with pre-built latest image: docker run -i --rm --name om-server -p 5080:5080 -p 1935:1935 openmeetings-docker-registry.bintray.io/server:latest
Works for me as expected
docker: Error response from daemon: unauthorized: Repository '/openmeetings/registry' does not support Docker API version v2.
~$ docker run -i --rm --name om-server -p 5080:5080 -p 1935:1935 openmeetings-docker-registry.bintray.io/server:latest
Unable to find image 'openmeetings-docker-registry.bintray.io/server:latest' locally
docker: Error response from daemon: unauthorized: Repository '/openmeetings/registry' does not support Docker API version v2.
See 'docker run --help'.
Docker version 17.09.0-ce, build afdb6d4
I have tested on Ubuntu 16.04
Client:
Version: 17.05.0-ce
API version: 1.29
Go version: go1.7.5
Git commit: 89658be
Will try to check on Ubuntu 17.10 and find workaround ...
Client:
Version: 17.09.0-ce
API version: 1.32
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:42:18 2017
Also works on my machine, will double-check tonight on different machine
Seems to be reproducible :(((( Will try to find what is wrong :(
I am getting exactly the same today on Ubuntu 16.04 using a plain vanilla docker build with today's image. Also seeing this during build: at org.apache.commons.dbcp2.BasicDataSource.validateConnectionFactory(BasicDataSource.java:2304) at org.apache.commons.dbcp2.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:2290) ... 33 common frames omitted Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
Just for info
I experienced the same problem. I solved it by switching to MariaDB instead, by doing the following
apt-get install mysql-server mysql-client
with apt-get install mariadb-server mariadb-client
-u root -p${DB_ROOT_PASS}
from the mysql calls in scripts/om_install.sh, they aren't necessary with MariaDB for unix socket connectionsHopefully I was able to fix this Could you try new image:
docker run -i --rm --name om-server -p 5080:5080 -p 1935:1935 openmeetings-docker-images.bintray.io/server:latest
Just a quick question? Is there any persistence built into this image?
What do you mean by persistence?
Simple example, if you installed some new features in the Docker Image, and you unloaded and reloaded the docker, would the changes survive? They won't unless you have some special strategy.
This is my first docker image :) It is created to simplify "run and test" process :)
PRs are welcome :) The only "special strategy" I can imagine is to use external DB :) ....
There are 'Data Volumes' and other strategies. http://www.computerweekly.com/feature/Docker-storage-how-to-get-persistent-storage-in-Docker
Thanks! Will try to check these docs and add persistence
your instructions work now. thanks you can probably close this
Thanks for checking!
I have an ubuntu VM created with vagrant, installed docker with debops.docker ansible role, cloned this repo, and typed
docker build .
it failed to start mysql.
does the master branch work? should I try another git-tagged version, check that out and build again?
I'll update with the error message. Just wondering how well supported this project is