Failed fetching stories because the server is down

I am running into an issue after switching to using the “chrome.docker” target.

When I try to run the loki test command (after ensuring the storybook server has been started and is running), I get the following error:

However, if I build storybook, and run loki --reactUri file:./build-storybook, it works fine.

This is my current loki configuration:

  "loki": {
    "chromeTolerance": 3,
    "configurations": {
      "chome.largeScreen": {
        "target": "chrome.docker",
        "width": 1920,
        "height": 1080,
        "deviceScaleFactor": 1,
        "mobile": false,
        "fitWindow": false
      },
      "chrome.laptop": {
        "target": "chrome.docker",
        "width": 1366,
        "height": 768,
        "deviceScaleFactor": 1,
        "mobile": false,
        "fitWindow": false
      }
    }
  }

I am not too familiar with Docker, so this might be a stupid question, but do I need to somehow start the storybook server inside the Docker container? I’d appreciate any help here.

Issue Analytics

State:
Created 4 years ago
Reactions:5
Comments:9

Top GitHub Comments

1reaction

jWytrzescommented, Mar 9, 2022

Any updates? I am encountering this issue with target set to chrome.docker and also chrome.app. Loki doesn’t see the storybook server on the default port nor some other port. It works fine with static build

1reaction

petr7555commented, Apr 26, 2021

I have a similar question. When running loki test --port 6006 --configurationFilter chrome.laptop I need to start storybook on port 6006 in advance. If I run loki test --port 6006 --configurationFilter chrome.docker, do I need to start the storybook somehow?

My configurations:

configurations: {
    'chrome.laptop': {
      target: 'chrome.app',
      width: 414,
      height: 736,
    },
    'chrome.docker': {
      target: 'chrome.docker',
      width: 414,
      height: 736,
    },
    android: {
      target: 'android.emulator',
    },
  },