iBet uBet web content aggregator. Adding the entire web to your favor.
iBet uBet web content aggregator. Adding the entire web to your favor.



Link to original content: http://github.com/bespoken/bst/issues/650
Bst not working inside a docker container with node:14.0-alpine · Issue #650 · bespoken/bst · GitHub
Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

Bst not working inside a docker container with node:14.0-alpine #650

Open
dmarvp opened this issue May 8, 2020 · 2 comments
Open

Bst not working inside a docker container with node:14.0-alpine #650

dmarvp opened this issue May 8, 2020 · 2 comments
Assignees
@ecruzado
Labels
upcoming

Comments

@dmarvp
Copy link
Contributor

dmarvp commented May 8, 2020

Description:

When installing bst inside a docker container it won't execute tests.

Dockerfile:

FROM node:14.0-alpine
RUN apk add bash zip
RUN npm install bespoken-tools@latest -g
RUN bst -v

Steps To Reproduce

Steps to reproduce the behavior:

  1. Build a docker image with bst installed and run it
  2. Connect to the container
  3. Run bst test

Expected behavior

Tests should be executed correctly.

Actual behavior

The following error appears and bst is not executed:

(node:70) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:77) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
@jkelvie
Copy link
Member

jkelvie commented May 8, 2020

It works for me on the Docker images node:10, node:12 and node:14

I do get a warning on node:14 though.

@dmarvp dmarvp changed the title Bst not working inside a docker container Bst not working inside a docker container with node:14.0-alpine May 8, 2020
@dmarvp
Copy link
Contributor Author

dmarvp commented May 8, 2020

I think we would need to get rid of the warnings, but that certainly reduces the priority of this ticket. Removing the ticket from the current sprint now.

@dmarvp dmarvp added upcoming and removed sprint 58 labels May 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ecruzado ecruzado

Labels
upcoming
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jkelvie @ecruzado @dmarvp