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

Update documentation to clarify REPL usage and security implications #9

Open
swizzlr opened this Issue Dec 3, 2015 · 61 comments

Comments

Projects
None yet
@swizzlr
Contributor

swizzlr commented Dec 3, 2015

Overview

Swift REPL requires LLDB. LLDB requires some elevated privileges.

Objectives

  • Clearly define the elevated privileges required by LLDB's REPL
  • Provide clear and simple documentation in the README on how to access the REPL, including an explanation of the rationale required
  • Provide alternative examples of using the docker image that don't involve the REPL/elevated privileges (e.g. Dockerfiles, invoking scripts in Swift)
@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 3, 2015

Collaborator

The real was definitely working for me, but I was installing all the deps that apple was suggesting. Should we put those deps back for completeness sake? We might be breaking other parts of the toolchain without knowing it but not having deps apple details in their docs. Perhaps revert that commit and see what happens?

Collaborator

hamin commented Dec 3, 2015

The real was definitely working for me, but I was installing all the deps that apple was suggesting. Should we put those deps back for completeness sake? We might be breaking other parts of the toolchain without knowing it but not having deps apple details in their docs. Perhaps revert that commit and see what happens?

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Dec 3, 2015

Contributor

@hamin When they say "development dependencies" I assume they mean for building the swift toolchain itself. (right, @jckarter)? I'll work backwards from the list of dependencies and find which libraries are necessary; then I'll open a PR to the swift repo updating their docs.

Contributor

swizzlr commented Dec 3, 2015

@hamin When they say "development dependencies" I assume they mean for building the swift toolchain itself. (right, @jckarter)? I'll work backwards from the list of dependencies and find which libraries are necessary; then I'll open a PR to the swift repo updating their docs.

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 3, 2015

Collaborator

@swizzlr yeah what you're saying makes sense, checking it out

Collaborator

hamin commented Dec 3, 2015

@swizzlr yeah what you're saying makes sense, checking it out

@hamin hamin added the bug label Dec 3, 2015

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Dec 3, 2015

Contributor

@hamin just tried "reverting" those changes and no dice. are you sure it worked for you, back then? maybe it's flaky?

Contributor

swizzlr commented Dec 3, 2015

@hamin just tried "reverting" those changes and no dice. are you sure it worked for you, back then? maybe it's flaky?

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

So its working for me right now. I'm running latest master:

screen shot 2015-12-03 at 7 06 51 pm

Collaborator

hamin commented Dec 4, 2015

So its working for me right now. I'm running latest master:

screen shot 2015-12-03 at 7 06 51 pm

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

@swizzlr its working for me. I'm running latest master

Collaborator

hamin commented Dec 4, 2015

@swizzlr its working for me. I'm running latest master

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

@swizzlr what were you trying to run exactly?

Collaborator

hamin commented Dec 4, 2015

@swizzlr what were you trying to run exactly?

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

@swizzlr argh sorry its not running for me...i was running my old docker image...gimme a few

Collaborator

hamin commented Dec 4, 2015

@swizzlr argh sorry its not running for me...i was running my old docker image...gimme a few

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

@swizzlr confirmed this master is not working for me...the above screenshot was from my original repo. It definitely worked

Collaborator

hamin commented Dec 4, 2015

@swizzlr confirmed this master is not working for me...the above screenshot was from my original repo. It definitely worked

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Dec 4, 2015

Contributor

Does this commit work 369c495 ?

Contributor

swizzlr commented Dec 4, 2015

Does this commit work 369c495 ?

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

@swizzlr checking it out. Meanwhile do a docker pull from here https://hub.docker.com/r/harisamin/docker-swift/

docker pull harisamin/docker-swift

Try that and see if it works there

Collaborator

hamin commented Dec 4, 2015

@swizzlr checking it out. Meanwhile do a docker pull from here https://hub.docker.com/r/harisamin/docker-swift/

docker pull harisamin/docker-swift

Try that and see if it works there

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Dec 4, 2015

Contributor

Nope, not working on this (digital ocean VM hooked up with docker-machine).

docker run -it harisamin/docker-swift bash
Contributor

swizzlr commented Dec 4, 2015

Nope, not working on this (digital ocean VM hooked up with docker-machine).

docker run -it harisamin/docker-swift bash
@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Dec 4, 2015

Contributor

error: failed to launch REPL process: process launch failed: 'A' packet returned an error: 8

Contributor

swizzlr commented Dec 4, 2015

error: failed to launch REPL process: process launch failed: 'A' packet returned an error: 8

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

wtf how is it working for me then from my original image. you're just typing swift right? I know there's a swift_repl not sure what exactly that one does

Collaborator

hamin commented Dec 4, 2015

wtf how is it working for me then from my original image. you're just typing swift right? I know there's a swift_repl not sure what exactly that one does

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Dec 4, 2015

Contributor

We need a third person to try this out to figure out which of our machines is wrong. The image ID is c9f6b5fece4f, what's yours?

Contributor

swizzlr commented Dec 4, 2015

We need a third person to try this out to figure out which of our machines is wrong. The image ID is c9f6b5fece4f, what's yours?

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

The one I pushed to Docker Hub earlier today was this: harisamin/docker-swift latest 48660452cc49

screen shot 2015-12-03 at 7 25 46 pm

Collaborator

hamin commented Dec 4, 2015

The one I pushed to Docker Hub earlier today was this: harisamin/docker-swift latest 48660452cc49

screen shot 2015-12-03 at 7 25 46 pm

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

Again from original one I had.

screen shot 2015-12-03 at 7 28 35 pm

Collaborator

hamin commented Dec 4, 2015

Again from original one I had.

screen shot 2015-12-03 at 7 28 35 pm

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

@swizzlr master on our repo:

Step 7 : RUN wget https://swift.org/builds/ubuntu1404/swift-2.2-SNAPSHOT-2015-12-01-b/swift-2.2-SNAPSHOT-2015-12-01-b-ubuntu14.04.tar.gz
 ---> Running in 0e5501001ce0
--2015-12-04 00:32:30--  https://swift.org/builds/ubuntu1404/swift-2.2-SNAPSHOT-2015-12-01-b/swift-2.2-SNAPSHOT-2015-12-01-b-ubuntu14.04.tar.gz
Resolving swift.org (swift.org)... 169.45.67.140
Connecting to swift.org (swift.org)|169.45.67.140|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-12-04 00:32:30 ERROR 404: Not Found.

Checking if there's a new tar, maybe apple removed the old one

Collaborator

hamin commented Dec 4, 2015

@swizzlr master on our repo:

Step 7 : RUN wget https://swift.org/builds/ubuntu1404/swift-2.2-SNAPSHOT-2015-12-01-b/swift-2.2-SNAPSHOT-2015-12-01-b-ubuntu14.04.tar.gz
 ---> Running in 0e5501001ce0
--2015-12-04 00:32:30--  https://swift.org/builds/ubuntu1404/swift-2.2-SNAPSHOT-2015-12-01-b/swift-2.2-SNAPSHOT-2015-12-01-b-ubuntu14.04.tar.gz
Resolving swift.org (swift.org)... 169.45.67.140
Connecting to swift.org (swift.org)|169.45.67.140|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-12-04 00:32:30 ERROR 404: Not Found.

Checking if there's a new tar, maybe apple removed the old one

@hamin

This comment has been minimized.

Show comment
Hide comment
@lxcid

This comment has been minimized.

Show comment
Hide comment
@lxcid

lxcid Dec 4, 2015

On my own docker implementation I had user reporting the same issue. Funny thing is it work for my docker on VM.

lxcid commented Dec 4, 2015

On my own docker implementation I had user reporting the same issue. Funny thing is it work for my docker on VM.

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Dec 4, 2015

Contributor

@lxcid That's fascinating! Do you think you could find out what the implementations are?

Maybe this is a TTY thing?


I was interested in creating a latest image that would provide the most recent version built from source. Perhaps if we try building from scratch inside the container we might unearth the dependencies that are not present?

Contributor

swizzlr commented Dec 4, 2015

@lxcid That's fascinating! Do you think you could find out what the implementations are?

Maybe this is a TTY thing?


I was interested in creating a latest image that would provide the most recent version built from source. Perhaps if we try building from scratch inside the container we might unearth the dependencies that are not present?

@lxcid

This comment has been minimized.

Show comment
Hide comment
@lxcid

lxcid Dec 4, 2015

I'm trying to build from source at the moment though. Its painfully slow, maybe its because I'm building a release build.

Use the following python (2.7) script https://github.com/apple/swift/blob/master/utils/build-script

I'm not sure if I can wait until it complete but I'll keep you updated on my finding.

lxcid commented Dec 4, 2015

I'm trying to build from source at the moment though. Its painfully slow, maybe its because I'm building a release build.

Use the following python (2.7) script https://github.com/apple/swift/blob/master/utils/build-script

I'm not sure if I can wait until it complete but I'll keep you updated on my finding.

@lxcid

This comment has been minimized.

Show comment
Hide comment
@lxcid

lxcid Dec 4, 2015

root@ab75a4cb7eff:/usr/src/swift# ./build/Ninja-ReleaseAssert/swift-linux-x86_64/bin/swift --version
Swift version 2.2-dev (LLVM 46be9ff861, Clang 4deb154edc, Swift c959ce2c83)
Target: x86_64-unknown-linux-gnu
root@ab75a4cb7eff:/usr/src/swift# ./build/Ninja-ReleaseAssert/swift-linux-x86_64/bin/swift          
LLVM ERROR: Compiler-internal integrated REPL unimplemented for this platform

This is the output of the release build.

I'm doing another debug build at the moment.

lxcid commented Dec 4, 2015

root@ab75a4cb7eff:/usr/src/swift# ./build/Ninja-ReleaseAssert/swift-linux-x86_64/bin/swift --version
Swift version 2.2-dev (LLVM 46be9ff861, Clang 4deb154edc, Swift c959ce2c83)
Target: x86_64-unknown-linux-gnu
root@ab75a4cb7eff:/usr/src/swift# ./build/Ninja-ReleaseAssert/swift-linux-x86_64/bin/swift          
LLVM ERROR: Compiler-internal integrated REPL unimplemented for this platform

This is the output of the release build.

I'm doing another debug build at the moment.

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

@lxcid do u mind trying the latest master? I've tested the current master on my local docker instances and am able to launch the repl without issue. Let us know :)

Collaborator

hamin commented Dec 4, 2015

@lxcid do u mind trying the latest master? I've tested the current master on my local docker instances and am able to launch the repl without issue. Let us know :)

@lxcid

This comment has been minimized.

Show comment
Hide comment
@lxcid

lxcid Dec 4, 2015

I just tried the latest master fb7ff42 but it still have the same error in Digital Ocean docker.

I suspect it is the binary that have issue.

lxcid commented Dec 4, 2015

I just tried the latest master fb7ff42 but it still have the same error in Digital Ocean docker.

I suspect it is the binary that have issue.

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Dec 4, 2015

Contributor

@hamin you running it on your MB in boot2docker?

Contributor

swizzlr commented Dec 4, 2015

@hamin you running it on your MB in boot2docker?

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Dec 4, 2015

Collaborator

I installed docker via their official mac DMG.

sh --login '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'

That's how i start it its funny because looking at #12 seems like @sosedoff was able to deploy our image and it seems to be running.

Collaborator

hamin commented Dec 4, 2015

I installed docker via their official mac DMG.

sh --login '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'

That's how i start it its funny because looking at #12 seems like @sosedoff was able to deploy our image and it seems to be running.

@sosedoff

This comment has been minimized.

Show comment
Hide comment
@sosedoff

sosedoff Dec 4, 2015

Im running swift docker image: swiftdocker/swift:836d5b4ca56e and it works fine on both linux and osx machines. Locally (on osx) im using docker-machine and can run REPL with this command:

$ docker run -it swiftdocker/swift swift
Welcome to Swift version 2.2-dev (LLVM 46be9ff861, Clang 4deb154edc, Swift 778f82939c). Type :help for assistance.
  1>

sosedoff commented Dec 4, 2015

Im running swift docker image: swiftdocker/swift:836d5b4ca56e and it works fine on both linux and osx machines. Locally (on osx) im using docker-machine and can run REPL with this command:

$ docker run -it swiftdocker/swift swift
Welcome to Swift version 2.2-dev (LLVM 46be9ff861, Clang 4deb154edc, Swift 778f82939c). Type :help for assistance.
  1>
@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Jan 12, 2017

Contributor

@tianon thanks for the tip. we know it's something to do with accessing keyboard drivers in LLDB, but we might have more luck following up on their mailing list. In any case, REPL support is something rarely requested – most devs have their own local install of Swift that works just fine for that. It would be very nice to have a permanent solution.

Contributor

swizzlr commented Jan 12, 2017

@tianon thanks for the tip. we know it's something to do with accessing keyboard drivers in LLDB, but we might have more luck following up on their mailing list. In any case, REPL support is something rarely requested – most devs have their own local install of Swift that works just fine for that. It would be very nice to have a permanent solution.

@swizzlr swizzlr reopened this Jan 12, 2017

@swizzlr swizzlr changed the title from [BUG] REPL doesn't work. to [BUG] REPL doesn't work without without --privileged Jan 12, 2017

@swizzlr swizzlr changed the title from [BUG] REPL doesn't work without without --privileged to REPL doesn't work without without --privileged Jan 12, 2017

@aduermael

This comment has been minimized.

Show comment
Hide comment
@aduermael

aduermael Jan 13, 2017

@tianon @swizzlr @hamin that works:

docker run --cap-add sys_ptrace -ti --rm swiftdocker/swift swift

aduermael commented Jan 13, 2017

@tianon @swizzlr @hamin that works:

docker run --cap-add sys_ptrace -ti --rm swiftdocker/swift swift
@tianon

This comment has been minimized.

Show comment
Hide comment
@tianon

tianon Jan 13, 2017

@aduermael niiiice, I've confirmed that's working here too! That's way better. 🤘

tianon commented Jan 13, 2017

@aduermael niiiice, I've confirmed that's working here too! That's way better. 🤘

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Jan 13, 2017

Contributor

@tianon @aduermael Thanks so much Adrian! I will fold this into the documentation.

Contributor

swizzlr commented Jan 13, 2017

@tianon @aduermael Thanks so much Adrian! I will fold this into the documentation.

@swizzlr swizzlr changed the title from REPL doesn't work without without --privileged to REPL doesn't work without without --cap-add sys_ptrace Jan 13, 2017

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Jan 13, 2017

Contributor

So, to run the REPL we need to add the sys_ptrace key which allows you to "Trace arbitrary processes using ptrace(2)."

https://docs.docker.com/engine/reference/run/#/runtime-privilege-and-linux-capabilities

Now we just need to figure out how necessary that is, and if the REPL can run without it!

Contributor

swizzlr commented Jan 13, 2017

So, to run the REPL we need to add the sys_ptrace key which allows you to "Trace arbitrary processes using ptrace(2)."

https://docs.docker.com/engine/reference/run/#/runtime-privilege-and-linux-capabilities

Now we just need to figure out how necessary that is, and if the REPL can run without it!

@aduermael

This comment has been minimized.

Show comment
Hide comment
@aduermael

aduermael Jan 13, 2017

The Swift.org community makes use of the LLDB debugger to provide a rich REPL as well as the debugging environment for the Swift Language

@swizzlr the REPL uses LLDB, and LLDB needs ptrace...

https://swift.org/lldb/#why-combine-the-repl-and-debugger

aduermael commented Jan 13, 2017

The Swift.org community makes use of the LLDB debugger to provide a rich REPL as well as the debugging environment for the Swift Language

@swizzlr the REPL uses LLDB, and LLDB needs ptrace...

https://swift.org/lldb/#why-combine-the-repl-and-debugger

@LoiKos

This comment has been minimized.

Show comment
Hide comment
@LoiKos

LoiKos Jun 21, 2017

Hello, I download the latest official swift image from docker hub and there is still the problem with REPL.

mbp-de-loic:Orange loik$ docker run --cap-add sys_ptrace -ti --rm swift swift 
error: failed to launch REPL process: process launch failed: 'A' packet returned an error: 8
mbp-de-loic:Orange loikos$ docker images swift
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
swift               latest              d505ae70cb39        2 weeks ago         1.15 GB

Can't make it work even using --cap-add sys_ptrace but it work with --privileged

@swizzlr @hamin

LoiKos commented Jun 21, 2017

Hello, I download the latest official swift image from docker hub and there is still the problem with REPL.

mbp-de-loic:Orange loik$ docker run --cap-add sys_ptrace -ti --rm swift swift 
error: failed to launch REPL process: process launch failed: 'A' packet returned an error: 8
mbp-de-loic:Orange loikos$ docker images swift
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
swift               latest              d505ae70cb39        2 weeks ago         1.15 GB

Can't make it work even using --cap-add sys_ptrace but it work with --privileged

@swizzlr @hamin

@andradei

This comment has been minimized.

Show comment
Hide comment
@andradei

andradei Sep 8, 2017

Had to add --privileged like @LoiKos mentioned. Maybe it is time to update the README that is shown on https://hub.docker.com/_/swift/

andradei commented Sep 8, 2017

Had to add --privileged like @LoiKos mentioned. Maybe it is time to update the README that is shown on https://hub.docker.com/_/swift/

@tianon

This comment has been minimized.

Show comment
Hide comment
@tianon

tianon Sep 8, 2017

tianon commented Sep 8, 2017

@hamin

This comment has been minimized.

Show comment
Hide comment
@hamin

hamin Sep 8, 2017

Collaborator

this one is tough and has been haunting us forever :) . Not sure what to do here, in the Github readme we have privileged noting that ppl use containers locally for development too and not just for deployments, places where a Swift repl is more needed or helpful. I think we decided to exclude them from the Docker hub documentation specifically for containers on linux servers concern. I think this was also pointed to us out by Docker team when we were merging the project in the official images section that they maintain.

Collaborator

hamin commented Sep 8, 2017

this one is tough and has been haunting us forever :) . Not sure what to do here, in the Github readme we have privileged noting that ppl use containers locally for development too and not just for deployments, places where a Swift repl is more needed or helpful. I think we decided to exclude them from the Docker hub documentation specifically for containers on linux servers concern. I think this was also pointed to us out by Docker team when we were merging the project in the official images section that they maintain.

@aduermael

This comment has been minimized.

Show comment
Hide comment
@aduermael

aduermael Sep 8, 2017

@tianon

Sounds like more caps are now required than before

Unfortunately, even with --cap-add=ALL, I can't make it work... 😕

aduermael commented Sep 8, 2017

@tianon

Sounds like more caps are now required than before

Unfortunately, even with --cap-add=ALL, I can't make it work... 😕

@tianon

This comment has been minimized.

Show comment
Hide comment
@tianon

tianon Sep 8, 2017

tianon commented Sep 8, 2017

@tianon

This comment has been minimized.

Show comment
Hide comment
@tianon

tianon Sep 8, 2017

tianon commented Sep 8, 2017

@tianon

This comment has been minimized.

Show comment
Hide comment
@tianon

tianon Sep 8, 2017

Ok, here's what I've had success with: (where default.json comes from https://raw.githubusercontent.com/docker/docker-ce/v17.06.2-ce/components/engine/profiles/seccomp/default.json)

--- default.json	2017-09-08 15:02:37.061507178 -0700
+++ swift.json	2017-09-08 15:02:54.821989684 -0700
@@ -216,6 +216,7 @@
 				"open",
 				"openat",
 				"pause",
+				"personality",
 				"pipe",
 				"pipe2",
 				"poll",
$ docker run -it --rm --security-opt seccomp=swift.json --cap-add sys_ptrace swift swift
Welcome to Swift version 3.1 (swift-3.1-RELEASE). Type :help for assistance.
  1>  

tianon commented Sep 8, 2017

Ok, here's what I've had success with: (where default.json comes from https://raw.githubusercontent.com/docker/docker-ce/v17.06.2-ce/components/engine/profiles/seccomp/default.json)

--- default.json	2017-09-08 15:02:37.061507178 -0700
+++ swift.json	2017-09-08 15:02:54.821989684 -0700
@@ -216,6 +216,7 @@
 				"open",
 				"openat",
 				"pause",
+				"personality",
 				"pipe",
 				"pipe2",
 				"poll",
$ docker run -it --rm --security-opt seccomp=swift.json --cap-add sys_ptrace swift swift
Welcome to Swift version 3.1 (swift-3.1-RELEASE). Type :help for assistance.
  1>  
@Khalian

This comment has been minimized.

Show comment
Hide comment
@Khalian

Khalian Sep 11, 2017

Contributor

Should we even be supporting repl in the official image? If things like text editors are excluded, everything except the core compiler and runtime should be excluded right? The purpose of this image is execution, not dev support.

Contributor

Khalian commented Sep 11, 2017

Should we even be supporting repl in the official image? If things like text editors are excluded, everything except the core compiler and runtime should be excluded right? The purpose of this image is execution, not dev support.

@jonauz

This comment has been minimized.

Show comment
Hide comment
@jonauz

jonauz Oct 14, 2017

So what is the way to make this docker work? As I keep getting error: failed to launch REPL process: process launch failed: 'A' packet returned an error: 8 no matter what I try to copy from here to my terminal.
Can't pass even first step to install this docker. I'm not familiar with REPL, so definitely have no clue how to set up it, just following readme, which is not working.

jonauz commented Oct 14, 2017

So what is the way to make this docker work? As I keep getting error: failed to launch REPL process: process launch failed: 'A' packet returned an error: 8 no matter what I try to copy from here to my terminal.
Can't pass even first step to install this docker. I'm not familiar with REPL, so definitely have no clue how to set up it, just following readme, which is not working.

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Nov 10, 2017

Contributor

@jonauz If the Readme instructions aren't working for you, please open a separate issue. This issue tracks the fact that the REPL fails without elevated security privileges.

Contributor

swizzlr commented Nov 10, 2017

@jonauz If the Readme instructions aren't working for you, please open a separate issue. This issue tracks the fact that the REPL fails without elevated security privileges.

@swizzlr swizzlr changed the title from REPL doesn't work without without --cap-add sys_ptrace to Update documentation to clarify REPL usage and security implications Nov 10, 2017

@swizzlr

This comment has been minimized.

Show comment
Hide comment
@swizzlr

swizzlr Nov 10, 2017

Contributor

Action item: me to update Readme and sync it with official repo README.

Contributor

swizzlr commented Nov 10, 2017

Action item: me to update Readme and sync it with official repo README.

@swizzlr swizzlr self-assigned this Nov 10, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment