Skip to content

Dockerize repo#40

Closed
hex337 wants to merge 2 commits intosimap:masterfrom
hex337:dockerize-repo
Closed

Dockerize repo#40
hex337 wants to merge 2 commits intosimap:masterfrom
hex337:dockerize-repo

Conversation

@hex337
Copy link
Copy Markdown

@hex337 hex337 commented Dec 14, 2022

  • Adds a Dockerfile
  • Adds a docker compose file
  • Update react-script
  • Update README

* Adds a Dockerfile
* Adds a docker compose file
* Update react-script
@netmindz
Copy link
Copy Markdown

Does the auto discovery of the PixelBlaze work?

@hex337
Copy link
Copy Markdown
Author

hex337 commented Dec 15, 2022

Working through that bit now, this is the error I get:

firestorm  | Error: connect ECONNREFUSED 172.26.0.1:81
firestorm  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16)
firestorm  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
firestorm  |   errno: -111,
firestorm  |   code: 'ECONNREFUSED',
firestorm  |   syscall: 'connect',
firestorm  |   address: '172.26.0.1',
firestorm  |   port: 81
firestorm  | }
firestorm  | ws not alive 172.26.0.1
firestorm  | stopping 172.26.0.1

Going to try using host networking on the container.

@hex337
Copy link
Copy Markdown
Author

hex337 commented Dec 15, 2022

Ok, I think this will only work in linux right now, since the host networking mode is only supported there. Bummer.

@netmindz
Copy link
Copy Markdown

I've not used firestorm yet, so don't know if the auto discovery is a convenient or critical aspect

@netmindz
Copy link
Copy Markdown

Working through that bit now, this is the error I get:

firestorm  | Error: connect ECONNREFUSED 172.26.0.1:81
firestorm  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16)
firestorm  |     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
firestorm  |   errno: -111,
firestorm  |   code: 'ECONNREFUSED',
firestorm  |   syscall: 'connect',
firestorm  |   address: '172.26.0.1',
firestorm  |   port: 81
firestorm  | }
firestorm  | ws not alive 172.26.0.1
firestorm  | stopping 172.26.0.1

Going to try using host networking on the container.

That is talking about port 81, where as I see no reference to that in your config, might need to expose port 81 too

@hex337
Copy link
Copy Markdown
Author

hex337 commented Dec 19, 2022

Played with the host networking option, but it's only supported in linux for now, so closing this until that changes.

@hex337 hex337 closed this Dec 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants