[bug]: When venia is hosted on docker, network requests run queued

[skisielewicz9bits]

Describe the bug

We are facing performance issues in our project based on venia concept, main issue for now are as in the topic queued requests ran from storefront. When we launch the upward server on main OS(Ubuntu 21.10) everything seems fine as in the screenshoot below: The problem starts when app is dockerized: Venia demo is facing same issue as I described:

To reproduce

Steps to reproduce the behavior:

Run any implementation based on pwa studio dockerized, check devtools network requests waterfall for xhr/fetch requests.

Expected behavior

Parallel on dockerized app as it works without docker.

Please let us know what packages this bug is in regards to:

• [ ] venia-concept
• [ ] venia-ui
• [x] pwa-buildpack
• [ ] peregrine
• [ ] pwa-devdocs
• [x] upward-js
• [ ] upward-spec
• [ ] create-pwa

[m2-assistant[bot]]

Hi @skisielewicz9bits. Thank you for your report. To speed up processing of this issue, make sure that you provided sufficient information.

Add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[anthoula]

@magento export issue to JIRA project PWA as Bug

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/PWA-2777 is successfully created for this GitHub issue.

[OneCricketeer]

@skisielewicz9bits Would you mind sharing your docker-run command(s)?

[skisielewicz9bits]

@OneCricketeer hey, we are facing this issue on every setup(staging or local), here is my dockerfile for local development:

FROM node:16.6.0-alpine as build
WORKDIR /usr/src/app

RUN apk --no-cache --virtual add \
    python3 \
    make \
    g++ \
    yarn

COPY package.json yarn.lock ./

RUN yarn install --frozen-lockfile

COPY src ./src
COPY templates ./templates
COPY CENSORED-static ./CENSORED-static
COPY i18n ./i18n
COPY local-intercept.js babel.config.js server.js template.html template-dev.html upward.yml webpack.config.js .graphqlconfig magento-compatibility.js ./

ARG MAGENTO_BACKEND_URL
ARG CHECKOUT_BRAINTREE_TOKEN
ARG ENTRY_TEMPLATE_PATH
ARG GTM_CODE

CMD [ "yarn", "run", "watch"]

[OneCricketeer]

Thanks, but are you using any specific cpu arguments with docker run or in a docker compose file when running the container, for example?

[skisielewicz9bits]

No, commad that is launching container is based on that https://github.com/magento/pwa-studio/blob/develop/docker/run-docker

[OneCricketeer]

Thanks

I see that's using the included docker-compose. Just wanted to verify you're not modifying anything with that

[skisielewicz9bits]

@OneCricketeer no, we just added few env vars

[tuyennn]

@skisielewicz9bits any update or your workaround on this?

[glo82145]

@skisielewicz9bits We are not able to reproduce this issue by following the steps given above. Please help us know if any step is missing.

[glo82145]

As we have not received any update on the same, hence we are closing it. Please feel free to reopen in case of update.