-
Notifications
You must be signed in to change notification settings - Fork 54
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
Docker mm update #19
Comments
Hi, I just checked the Travis CI builds and it fails because it couldn't find Electron v3.0.13 for linux-armv6l: /opt/magic_mirror/node_modules/electron/install.js:49
throw err
^
Error: Failed to find Electron v3.0.13 for linux-armv6l at https://github.com/electron/electron/releases/download/v3.0.13/electron-v3.0.13-linux-armv6l.zip
at Request.<anonymous> (/opt/magic_mirror/node_modules/nugget/index.js:169:61)
at emitOne (events.js:115:13)
at Request.emit (events.js:210:7)
at Request.onRequestResponse (/opt/magic_mirror/node_modules/request/request.js:1062:10)
at emitOne (events.js:115:13)
at ClientRequest.emit (events.js:210:7)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:564:21)
at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23)
at TLSSocket.socketOnData (_http_client.js:453:20)
at emitOne (events.js:115:13)
The command '/bin/sh -c npm install --unsafe-perm --silent' returned a non-zero code: 1
The command "docker build -t $DOCKER_USER/docker-magicmirror:raspberry -f ./raspberry/Dockerfile ." exited with 1. Therefore Travis CI didn't push a new version to the Docker Hub. I'll check what the corse for this is. |
Any progress on this? Thanks. |
Hope this will be fixed soon. Thanks for all efforts. |
I am getting this on the non-armhf build as well. |
Any update? |
Any update on this? |
as long as this is not solved here you can use my setup. |
@khassel Thx, but the container is restarting every 5 to 10 seconds. I'll stick to this right now. |
Sorry for the late response. I’ll take another look at this. |
@trombonekenny @Tezzlicious @ax42 @khassel @idoodler I provided a fix for the issue in PR #25. The image was successfully updated. Could someone please verify, that everything works as expected? |
@bastilimbach This is not working on my side. I changed |
@idoodler Ah probably because I only added |
This is the output of manifest inspect. Looks good: Created manifest list docker.io/bastilimbach/docker-magicmirror:latest
{
"schemaVersion": 2,
"mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
"manifests": [
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"size": 3891,
"digest": "sha256:1489c63d25972d6cbfb2104b9dbcac1fb5cec3baff3002c97220f2b1929140c9",
"platform": {
"architecture": "amd64",
"os": "linux"
}
},
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"size": 3891,
"digest": "sha256:1489c63d25972d6cbfb2104b9dbcac1fb5cec3baff3002c97220f2b1929140c9",
"platform": {
"architecture": "arm",
"os": "linux"
}
},
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"size": 3891,
"digest": "sha256:1489c63d25972d6cbfb2104b9dbcac1fb5cec3baff3002c97220f2b1929140c9",
"platform": {
"architecture": "arm64",
"os": "linux"
}
}
]
} |
@bastilimbach I am not using plain docker, but balena-cloud. It looks like your image is working again. But I do have issues execute Issue:
|
@bastilimbach I am running on a Raspberry Pi 3 B+ (I won't response the next few hours because I have to sleep now) |
couldn't test earlier, now running on a raspi3 doesn't work for me, getting the
anyone with the same problem? |
Looking into the travis-file: Afaik you are building 3 times the same image for the architecture the travis job is running on, probably amd64. |
Mh, thats strange. I thought with the following line I would configure qemu and therefore compile in arm. Used to do that also with the old raspberry pi image. Maybe I need to add a docker run --rm --privileged multiarch/qemu-user-static:register --reset I will open a new issue. |
Hi
I have just installed mm using your docker image which is supposed to be the latest one as I checked in the docker hub that your files were updated 2 days ago.
However I get a message regarding updating my mm. I thought I had the latest one released 2 days ago i.e. 2.7.1. Can you please help ? I have already deleted the image on portainer and pulled the latest one but still no joy.
Also how do I check my mm version ? Do I have to login into mm container ? If yes what is the username ?
Thank you again.
The text was updated successfully, but these errors were encountered: