-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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-compose up fails with "superset_superset_1 exited with code 243" #6887
Comments
same issue |
same issue +1 |
The problem occurs only in development mode because the
When it gets up, on the container, the volume is mounted with root ownership (or whatever user starts docker-composer), and superset tries to run with its own user An ugly workaround is to add
|
I did replicate this error on Ubuntu, but not in macOS. I've noticed that docker manages the added volumes in slightly different ways in both systems, particularly the ownership of the folders, so I think that this error only happens in Linux. As it only happens on the dev env, and because of the mounted folders setup, chmod 777 on the superset/assets in the host computer, (not necessary in the docker folder) also helps with the issue... |
@gchehab I did modified version of of docker-compose/dockerfile/entrypoint that uses same tactic as official postgres image for docker; Run as root(instead of work) and in docker-entrypoint.sh
|
Well, it seems to me that it is a better approach than running superset as root, even if that is the case only on the docker container. |
Ok. Will do a PR for review. |
Dears, I had the same issue , but editing /root/superset/incubator-superset/contrib/docker/docker-compose.yml to make superset work as production instead of development resolved this issue , just comment the development and un-comment the production lines as below: SUPERSET_ENV: production |
Hi @ButeForce I tried ur suggestion and this time on doing docker-compose up didn't throw the 243 error. And shows everything running.
But when I try to open the link in browser it doesn't connect. http://localhost:8088. It does't connect. It works on my mac though without this 243 error. |
Ok it connects. However pls see this. I see some issue with UI loading of few features of server Superset. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
|
UI build steps
1.`npm run build`
2.`npm run dev`
3.reboot superset
Ryan Miao <notifications@github.com> 于2019年5月21日周二 上午11:12写道:
… [image: image]
<https://user-images.githubusercontent.com/11866078/58065627-efddcc00-7bb8-11e9-94da-efe7dfec7ff8.png>
I run superset by using docker-compose on master branch, the welcome page
and sqllab is always keep loading.
I only change docker-compose.yml
SUPERSET_ENV: production
#SUPERSET_ENV: development
```
How to fix it
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6887>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC27DJVGSGNOENUNJXRQ2VLPWNSDNANCNFSM4GXVBRYA>
.
|
Thanks for your reply. I just run
Which file should I modify? Dockerfile? |
If you don't do secondary development, you can use the community version docker image. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
docker-compose file |
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
latest git
Expected results
superset starts up without error
Actual results
superset_1 | npm ERR! path /home/superset/superset/assets/node_modules
superset_1 | npm ERR! code EACCES
superset_1 | npm ERR! errno -13
superset_1 | npm ERR! syscall mkdir
superset_1 | npm ERR! Error: EACCES: permission denied, mkdir '/home/superset/superset/assets/node_modules'
superset_1 | npm ERR! { [Error: EACCES: permission denied, mkdir '/home/superset/superset/assets/node_modules']
superset_1 | npm ERR! cause:
superset_1 | npm ERR! { Error: EACCES: permission denied, mkdir '/home/superset/superset/assets/node_modules'
superset_1 | npm ERR! type: 'OperationalError',
superset_1 | npm ERR! '$error': '$error',
superset_1 | npm ERR! cause:
superset_1 | npm ERR! { errno: -13,
superset_1 | npm ERR! code: 'EACCES',
superset_1 | npm ERR! syscall: 'mkdir',
superset_1 | npm ERR! path: '/home/superset/superset/assets/node_modules' },
superset_1 | npm ERR! isOperational: true,
superset_1 | npm ERR! errno: -13,
superset_1 | npm ERR! code: 'EACCES',
superset_1 | npm ERR! syscall: 'mkdir',
superset_1 | npm ERR! path: '/home/superset/superset/assets/node_modules' },
superset_1 | npm ERR! isOperational: true,
superset_1 | npm ERR! stack:
superset_1 | npm ERR! 'Error: EACCES: permission denied, mkdir '/home/superset/superset/assets/node_modules'',
superset_1 | npm ERR! type: 'OperationalError',
superset_1 | npm ERR! '$error': '$error',
superset_1 | npm ERR! errno: -13,
superset_1 | npm ERR! code: 'EACCES',
superset_1 | npm ERR! syscall: 'mkdir',
superset_1 | npm ERR! path: '/home/superset/superset/assets/node_modules' }
superset_1 | npm ERR!
superset_1 | npm ERR! The operation was rejected by your operating system.
superset_1 | npm ERR! It is likely you do not have the permissions to access this file as the current user
superset_1 | npm ERR!
superset_1 | npm ERR! If you believe this might be a permissions issue, please double-check the
superset_1 | npm ERR! permissions of the file and its containing directories, or try running
superset_1 | npm ERR! the command again as root/Administrator (though this is not recommended).
superset_1 |
superset_1 | npm ERR! A complete log of this run can be found in:
superset_1 | npm ERR! /home/superset/.npm/_logs/2019-02-15T09_24_16_955Z-debug.log
superset_superset_1 exited with code 243
Steps to reproduce
git clone https://github.com/apache/incubator-superset/
cd incubator-superset/contrib/docker
prefix with SUPERSET_LOAD_EXAMPLES=yes to load examples:
docker-compose run --rm superset ./docker-init.sh
you can run this command everytime you need to start superset now:
docker-compose up
EDIT:
additional infos:
CentOS Linux release 7.6.1810 (Core)
docker version:
Docker version 18.09.2, build 6247962
The text was updated successfully, but these errors were encountered: