19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
w
wangm23456
05/28/2021, 7:04 AMd
daniel
05/28/2021, 2:50 PMHi, could you double-check that your dagster package is actually on 0.11.10? The stack trace there is referencing a method that was renamed a couple of months ago.
Once you update your dagster library you may need to run the 'dagster instance migrate' command to add any missing talbes
w
wangm23456
05/31/2021, 2:40 AMI started dagster in a docker without host volume, so there were no updates in dagster.
The error only happend when I turn on dagit and dagster-daemon together.
nohup dagit -p 3001 -h 0.0.0.0 > /proc/1/fd/1 &nohup dagster-daemon run > /proc/1/fd/1 &d
daniel
05/31/2021, 3:48 AMWhat version of dagster are you using? the discussion post says 0.11.10, but the get_all_asset_keys function in your stack trace hasn’t existed in the codebase for a couple of months now - the mystery for us to solve is how some part of your system is still running very old dagster code.
w
wangm23456
06/01/2021, 7:07 AMI get success from https://github.com/dagster-io/dagster/tree/0.11.11/examples/deploy_docker. The multiple containers solved my error.