Tring deployments using docker - these jobs ran smoothly when running locally

dagster.core.errors.DagsterExecutionLoadInputError: Error occurred while loading input "cereals" of step "find_highest_protein_cereal":

  File "/usr/local/lib/python3.9/site-packages/dagster/core/execution/plan/execute_plan.py", line 228, in dagster_event_sequence_for_step
    for step_event in check.generator(step_events):
  File "/usr/local/lib/python3.9/site-packages/dagster/core/execution/plan/execute_step.py", line 315, in core_dagster_event_sequence_for_step
    for event_or_input_value in ensure_gen(
  File "/usr/local/lib/python3.9/site-packages/dagster/core/execution/plan/inputs.py", line 462, in load_input_object
    yield from _load_input_with_input_manager(input_manager, load_input_context)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/execution/plan/inputs.py", line 829, in _load_input_with_input_manager
    value = input_manager.load_input(context)
  File "/usr/local/lib/python3.9/contextlib.py", line 137, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/execution/plan/utils.py", line 73, in solid_execution_error_boundary
    raise error_cls(

The above exception was caused by the following exception:
FileNotFoundError: [Errno 2] No such file or directory: '/opt/dagster/dagster_home/storage/f1e2c896-1df1-40b3-9371-522f8d1698b5/download_cereals/result'

  File "/usr/local/lib/python3.9/site-packages/dagster/core/execution/plan/utils.py", line 47, in solid_execution_error_boundary
    yield
  File "/usr/local/lib/python3.9/site-packages/dagster/core/execution/plan/inputs.py", line 829, in _load_input_with_input_manager
    value = input_manager.load_input(context)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/storage/fs_io_manager.py", line 168, in load_input
    with open(filepath, self.read_mode) as read_obj:

Any idea what configuration I may have missed out???

Hi Kayvan, do you get this error when you run the example without any changes? One thing is you'll want to make sure that /tmp/io_manager_storage is included in the run launcher, here's what it is in the example:

run_launcher:
  module: dagster_docker
  class: DockerRunLauncher
  config:
    env_vars:
      - DAGSTER_POSTGRES_USER
      - DAGSTER_POSTGRES_PASSWORD
      - DAGSTER_POSTGRES_DB
    network: docker_example_network
    container_kwargs:
      volumes: # Make docker client accessible to any launched containers as well
        - /var/run/docker.sock:/var/run/docker.sock
        - /tmp/io_manager_storage:/tmp/io_manager_storage

No errors before changes Volume mount for some reason wasn't working earlier