Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build AppImage on Windows (service.electron.build) #4318

Closed
CodeDead opened this issue Oct 13, 2019 · 35 comments
Closed

Unable to build AppImage on Windows (service.electron.build) #4318

CodeDead opened this issue Oct 13, 2019 · 35 comments

Comments

@CodeDead
Copy link

CodeDead commented Oct 13, 2019

  • Version: 21.2.0

  • Target: linux AppImage

  • Description:
    Building a Linux AppImage on a Windows device has been unavailable for the past couple of months thanks to an outage. More information below.

error=Get https://service.electron.build/find-build-agent?no-cache=1eq6jtp: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

@stale
Copy link

stale bot commented Dec 14, 2019

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the backlog label Dec 14, 2019
@CodeDead
Copy link
Author

This is still relevant and has not been addressed yet.

cannot get, wait error=Get https://service.electron.build/find-build-agent?no-cache=1evftno: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
attempt=1
waitTime=4

Get https://service.electron.build/find-build-agent?no-cache=1evftno: dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

@stale stale bot removed the backlog label Dec 16, 2019
@matvelloso
Copy link

FYI I seem to be stuck with the same error...

@kavil
Copy link

kavil commented Dec 18, 2019

same error...

@CodeDead CodeDead changed the title Unable to build AppImage (service.electron.build) Unable to build AppImage on Windows (service.electron.build) Dec 18, 2019
@rowalski
Copy link

rowalski commented Jan 9, 2020

i am getting this same error trying to build for debian...

@mastastealth
Copy link

mastastealth commented Feb 1, 2020

Same error here on Win 7, just trying a simple --linux build with defaults.

@ThummalaJanardhanReddy
Copy link

Is there any fix or work around for this.

@CodeDead
Copy link
Author

Is there any fix or work around for this.

Building directly on a linux system. You can also build windows images on linux using Wine.

@seannowotny
Copy link

Has anyone had luck with the Windows Linux Subsystem?

@AstroGD
Copy link

AstroGD commented Apr 1, 2020

Same issue here. Trying to build linux package for snap using electron-builder --linux snap

@o5k
Copy link

o5k commented May 11, 2020

Why is this still not addressed after half a year???

@CodeDead
Copy link
Author

@o5k It's a free service after all, and you can still create Linux builds on a Linux host (and Windows builds using wine on Linux).

@shickk
Copy link

shickk commented Jun 23, 2020

Same error. Any updates?

@alduish
Copy link

alduish commented Jul 5, 2020

I have the same error with deb and appImage I go to the site and this site is down

@kurone-kito
Copy link

I have the same error on Windows 10.
Curiously, if I try the same project on macOS, it doesn't reproduce.

@CodeDead
Copy link
Author

I have the same error on Windows 10.
Curiously, if I try the same project on macOS, it doesn't reproduce.

Electron builder supports building Windows binaries on non-Windows machines. See:
https://www.electron.build/multi-platform-build

This is also a work-around for this problem. You can use a Linux/macOS build machine to provide both the platform's own binaries and Windows binaries.

@stale
Copy link

stale bot commented Sep 10, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the backlog label Sep 10, 2020
@o5k
Copy link

o5k commented Sep 10, 2020

still relevant

@stale stale bot removed the backlog label Sep 10, 2020
@fairking
Copy link

fairking commented Sep 17, 2020

"electron": "^10.1.2",
"electron-builder": "^22.8.1",

Got the same error today. Trying to build on windows 10 with electron-builder --linux snap.
The error:

cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1fm6tp0": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
                      attempt=0
                      waitTime=2
  • cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1fm6tp0": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
                      attempt=1
                      waitTime=4
  • cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1fm6tp0": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
                      attempt=2
                      waitTime=6
  ⨯ Get "https://service.electron.build/find-build-agent?no-cache=1fm6tp0": dial tcp 51.15.76.176:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
  ⨯ C:\Code\electron-cgi-calculator-demo\node_modules\app-builder-bin\win\x64\app-builder.exe exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE  stackTrace=
Error: C:\Code\electron-cgi-calculator-demo\node_modules\app-builder-bin\win\x64\app-builder.exe exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
at ChildProcess.childProcess.once.code (C:\Code\electron-cgi-calculator-demo\node_modules\builder-util\src\util.ts:243:14)
at Object.onceWrapper (events.js:286:20)
at ChildProcess.emit (events.js:198:13)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
From previous event:
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
From previous event:
at RemoteBuilder.build (C:\Code\electron-cgi-calculator-demo\node_modules\app-builder-lib\src\remoteBuilder\RemoteBuilder.ts:52:28)
at RemoteTarget.finishBuild (C:\Code\electron-cgi-calculator-demo\node_modules\app-builder-lib\src\linuxPackager.ts:99:30)

@Darkseal
Copy link

Darkseal commented Oct 6, 2020

Unfortunately the https://service.electron.build has been down since months and it doesn't seem that such issue will be fixed anytime soon, as we can see from the amount of (mostly open) GitHub issues that have been opened from users that are trying to deal with such problem in the past months.

Here's a viable alternative to build a redistributable Linux package on a Windows 10 environment: I'll try to explain it using a step-by-step approach in order to make it as easy as possible for those who don't know Docker well.

  • Install Docker from here
  • Download the electronuserland/builder Docker image with the following console command:
    docker pull electronuserland/builder
  • From the Electron project's root folder (such as C:\MyApp), type the following command-line command to run the container and map the Electron project's root folder to the /project virtual path:
    docker run -rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder
  • From inside the container, type the following commands to upgrade the Electron project's Yarn packages, globally install the electron-builder package and build the Linux redistributable package:
cd /project
yarn upgrade
yarn global add electron-builder
electron-builder -l

If everything went smooth, you should be able to locate your MyApp.deb file (or rpm, AppImage, or anything you've configured within the electron-builder's package.json file) inside the Electron project's /dist/ folder.

For further info about this whole procedure and a bit of background, check out this post on my blog.

@JasonkayZK
Copy link

Unfortunately the https://service.electron.build has been down since months and it doesn't seem that such issue will be fixed anytime soon, as we can see from the amount of (mostly open) GitHub issues that have been opened from users that are trying to deal with such problem in the past months.

Here's a viable alternative to build a redistributable Linux package on a Windows 10 environment: I'll try to explain it using a step-by-step approach in order to make it as easy as possible for those who don't know Docker well.

  • Install Docker from here
  • Download the electronuserland/builder Docker image with the following console command:
    docker pull electronuserland/builder
  • From the Electron project's root folder (such as C:\MyApp), type the following command-line command to run the container and map the Electron project's root folder to the /project virtual path:
    docker run -rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder
  • From inside the container, type the following commands to upgrade the Electron project's Yarn packages, globally install the electron-builder package and build the Linux redistributable package:
cd /project
yarn upgrade
yarn global add electron-builder
electron-builder -l

If everything went smooth, you should be able to locate your MyApp.deb file (or rpm, AppImage, or anything you've configured within the electron-builder's package.json file) inside the Electron project's /dist/ folder.

For further info about this whole procedure and a bit of background, check out this post on my blog.

It works,but the command should be:
docker run --rm -ti -v C:\MyApp\:/project -w /project electronuserland/builder
The -rm flag should be --rm

@stale
Copy link

stale bot commented Jan 9, 2021

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the backlog label Jan 9, 2021
@CodeDead
Copy link
Author

CodeDead commented Jan 9, 2021

This is still relevant.

@stale stale bot removed the backlog label Jan 9, 2021
@snaildos
Copy link

snaildos commented Feb 1, 2021

This is pathetic? Electron is used everywhere, and now we can't even build linux images?
That's funny.
Seriously.
What in the world is actually going on here?

@CodeDead
Copy link
Author

CodeDead commented Feb 2, 2021

Multiple workarounds have already been discussed here @snaildos . This is still a free service and one should not expect free things to last or remain free and accessible for everyone for eternity.

You're free to host your own build service for the world to use, of course.

@snaildos
Copy link

snaildos commented Feb 3, 2021

Alright. So if I where too host my own build service, how do I change the electron-builder default build server URL?

@newalphamedia
Copy link

I'd like to know how to host my own service and change the build server URL also.

@snaildos
Copy link

snaildos commented Apr 9, 2021

Not worth it tbh, just get bare metal Linux machine and install wine. Run builds etc on there. :)

@mmaietta
Copy link
Collaborator

mmaietta commented Apr 10, 2021

The only reference to that URL in this repo that I can find in the code is this:

<env name="BUILD_AGENT_HOST" value="service.electron.build" />

There's this repo+readme with info on how to host your own service: https://github.com/electron-userland/electron-build-service/blob/master/self-hosted.md

If you can point me as to where this build server URL needs to be configured in this repo such that you're able to use your own build service, I can happily take a look at having that configurable (if not, just a local patch file for the interim)

Also related, if you're ever interested in submitting a quick fix or collaborate on a larger feature, here are easy instructions for setting up a local dev env:
https://github.com/electron-userland/electron-builder/blob/master/CONTRIBUTING.md#to-setup-a-local-dev-environment

For context, I think there are only a couple of maintainers active on this project, so I'd happily accept contributions. (I only joined a couple months ago) 🙂

@rzfzr
Copy link

rzfzr commented Apr 29, 2021

No luck with @Darkseal and @JasonkayZK solution, it creates the project dir but with no contents, any ideas?

@JasonkayZK
Copy link

No luck with @Darkseal and @JasonkayZK solution, it creates the project dir but with no contents, any ideas?

No better ideas yet! 😞

I tried to use virtual machine such as Ubuntu or MacOS mirror in VMWare to build and test for multiple-platform. It works!
Maybe you can try different environment in GIthub-Actions. 😄

@mmaietta
Copy link
Collaborator

mmaietta commented May 9, 2021

I guess to close out this issue officially, we just need these instructions tidied up for adding to the docs?
#4318 (comment)

I think it's safe to assume for an issue >1yr old that server is dead and will remain so, so providing instructions on how to run your own seems like a fair fallback option.

@stale
Copy link

stale bot commented Jul 9, 2021

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the backlog label Jul 9, 2021
@sleeyax
Copy link

sleeyax commented Jul 9, 2021

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Still relevant :/

@stale stale bot removed the backlog label Jul 9, 2021
@mmaietta
Copy link
Collaborator

mmaietta commented Jul 9, 2021

Still relevant and still no plans for restarting the service. The service is dead. Closing this

@mmaietta mmaietta closed this as completed Jul 9, 2021
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

No branches or pull requests