Closed shenweiyan closed 3 days ago
Hey I have been having similar issues but managed to fix it recently, can I have more information on your host distribution ?
Personal experience was :
Ubuntu-20.04 WSL2 (no GUI) : worked (Docker run)
Ubuntu-20.04 VMWare on ESXi (Gnome GUI) : didn't work (Docker run
and Docker-compose up -d
)
Debian 10 VMWare on ESXi (no GUI) : worked (Docker-compose up -d
)
I can share my docker-compose.yml if needed
Possible reasons : VMWare machines' way of interacting with assembly to build GUI might interfere with Docker's build. 有问题的话 中文也行 *if there is any trouble, chinese is also ok
Hey I have been having similar issues but managed to fix it recently, can I have more information on your host distribution ? Personal experience was : Ubuntu-20.04 WSL2 (no GUI) : worked (Docker run) Ubuntu-20.04 VMWare on ESXi (Gnome GUI) : didn't work (
Docker run
andDocker-compose up -d
) Debian 10 VMWare on ESXi (no GUI) : worked (Docker-compose up -d
) I can share my docker-compose.yml if neededPossible reasons : VMWare machines' way of interacting with assembly to build GUI might interfere with Docker's build. 有问题的话 中文也行 *if there is any trouble, chinese is also ok
It's great. Below is my host distribution information, maybe I should make some test on Ubuntu/Debian.
$ cat /proc/version
Linux version 3.10.0-957.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Thu Nov 8 23:39:32 UTC 2018
$ lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.6.1810 (Core)
Release: 7.6.1810
Codename: Core
By the way, you can speak Chinese?
会讲中文
Yes in my opinion Debian 10 with no GUI is the most straightforward installation that might work on many hardware installations (tried on ESXi and a PC both were smooth)
会讲中文
Yes in my opinion Debian 10 with no GUI is the most straightforward installation that might work on many hardware installations (tried on ESXi and a PC both were smooth)
谢谢。难得在这里还能遇到一个可以中文交流的热心维护者,您是中国人也在国内做 Galaxy 的一些开发吗?
I am having the same problem in two trials with Ubuntu and CentOs VMs. Trying docker-compose
on the base compose yaml
I get the error related to issue 588. Any news on that?
@martinbsurfsara and I are seeing the same, it looks like a database migration issue. I see this above here
sqlalchemy.exc.IntegrityError: (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "pg_type_typname_nsp_index"
DETAIL: Key (typname, typnamespace)=(kombu_message, 2200) already exists.
[SQL:
CREATE TABLE kombu_message (
id INTEGER NOT NULL,
visible BOOLEAN,
timestamp TIMESTAMP WITHOUT TIME ZONE,
payload TEXT NOT NULL,
version SMALLINT NOT NULL,
queue_id INTEGER,
PRIMARY KEY (id),
CONSTRAINT "FK_kombu_message_queue" FOREIGN KEY(queue_id) REFERENCES kombu_queue (id)
)
And locally running the container and checking the uwsgi.log file I see
migrate.versioning.script.base DEBUG 2021-11-09 12:42:13,036 [p:1430,w:0,m:0] [MainThread] Loading script lib/galaxy/model/migrate/versions/0162_job_only_pjas.py...
migrate.versioning.script.base DEBUG 2021-11-09 12:42:13,036 [p:1430,w:0,m:0] [MainThread] Script lib/galaxy/model/migrate/versions/0162_job_only_pjas.py loaded successfully
migrate.versioning.repository DEBUG 2021-11-09 12:42:13,036 [p:1430,w:0,m:0] [MainThread] Repository lib/galaxy/model/migrate loaded successfully
migrate.versioning.repository DEBUG 2021-11-09 12:42:13,037 [p:1430,w:0,m:0] [MainThread] Config: OrderedDict([('db_settings', OrderedDict([('repository_id', 'Galaxy'), ('version_table', 'migrate_version'), ('required_dbs', '[]')]))])
Traceback (most recent call last):
File "lib/galaxy/webapps/galaxy/buildapp.py", line 48, in app_factory
app = galaxy.app.UniverseApplication(global_conf=global_conf, **kwargs)
File "lib/galaxy/app.py", line 97, in __init__
self._configure_models(check_migrate_databases=self.config.check_migrate_databases, check_migrate_tools=check_migrate_tools, config_file=config_file)
File "lib/galaxy/config/__init__.py", line 1226, in _configure_models
create_or_verify_database(db_url, config_file, self.config.database_engine_options, app=self, map_install_models=combined_install_database)
File "lib/galaxy/model/migrate/check.py", line 140, in create_or_verify_database
raise Exception("{}. {}{}".format(expect_msg, instructions, backup_msg))
Exception: Your database has version '1' but this code expects version '170'. Please backup your database and then migrate the database schema by running 'sh manage_db.sh upgrade'.
@bgruening not sure if you've seen this?
potential duplicate of https://github.com/bgruening/docker-galaxy-stable/issues/575
Thanks to @jyotipm29 we are back on track :smile: The new 24.1 image contains a lot of changes and reflects the latest developments in Galaxy. I would like to close this PR, but please feel free to reopen and rebase against the latest version.
Please give it a try:
docker run -p 8080:80 -p 8021:21 -p 4002:4002 --privileged=true -e "GALAXY_DESTINATIONS_DEFAULT=slurm_cluster_docker" -v /tmp/galaxy-data/:/export/ quay.io/bgruening/galaxy:24.1
... or any other combination. The readme has been updated. Please add any useful tip to it.
For a list of changes, see the Changelog.
I have tried to install docker-galaxy-stable, however, is there a problem that doesn't work correctly, it seems docker galaxy cannot start normally. The following is the log information at startup:
any idea what happens? Thanks so much