-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
V3 API S3 Datasource root user not allowed #3548
Comments
oh actually it doesn't even work as a new user
I've already spent more time on this than I care to. Guess I'll stick with API v2 for now |
FYI, the situation that caused this error was likely fixed in nbconvert 6.2 (see jupyter/nbconvert#1646), released a few weeks ago. |
Interesting! thanks for taking a look. but it seems like I was already using (my Pipfile.lock looks like this) "nbconvert": {
"hashes": [
"sha256:16ceecd0afaa8fd26c245fa32e2c52066c02f13aa73387fffafd84750baea863",
"sha256:b1b9dc4f1ff6cafae0e6d91f42fb9046fdc32e6beb6d7e2fa2cd7191ad535240"
],
"markers": "python_version >= '3.7'",
"version": "==6.2.0"
}, maybe it is something else |
You may need to reinstall after moving to nbconvert 6.2, or clean up the erroneous files, as a previous version might have created those files with the wrong permissions. See some of the steps people had to do in jupyter/nbconvert#1430. What 6.2 does is not create the problem in the future, but it won't fix the problems created by previous versions of nbconvert. |
Thanks @chapmanjacobd and @jasongrout! To confirm, is this still an issue? |
hmmm I still get the same error even with a new venv created under the normal user account actually it wasn't the same Pipfile I just did
but same error so 🤷♂️
|
Describe the bug
Jupyter doesn't allow running as root user even though we live in the container universe whether we like it or not
To Reproduce
Steps to reproduce the behavior:
Expected behavior
This is the first program I've run into where I've had to create another user account just to run it. Mildly annoying but maybe not worth fixing either. v2 Datasource ran fine but I wanted to try out v3.
Environment (please complete the following information):
Additional context
Workaround:
The text was updated successfully, but these errors were encountered: