# Problem invoking \`--bug-report=rr\` in a docker image. I have the following package

**URL:** <https://discourse.julialang.org/t/problem-invoking-bug-report-rr-in-a-docker-image-i-have-the-following-package/57134>\
**Category:** General Usage\
**Created:** [March 14, 2021, 4:12pm UTC](https://discourse.julialang.org/t/problem-invoking-bug-report-rr-in-a-docker-image-i-have-the-following-package/57134 "2021-03-14T16:12:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BridgeBot](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bridgebot/32/21491_2.png) [@BridgeBot](https://discourse.julialang.org/u/BridgeBot)\
**Post date:** [March 14, 2021, 4:12pm UTC](https://discourse.julialang.org/t/problem-invoking-bug-report-rr-in-a-docker-image-i-have-the-following-package/57134/1 "2021-03-14T16:12:45Z")

</div>

Problem invoking `--bug-report=rr` in a docker image. I have the following packages installed in the Debian image:

```julia
      Status `~/.julia/environments/v1.6/Project.toml`
  [bcf9a6e7] BugReporting v0.1.3
  [7073ff75] IJulia v1.23.2
  [c3e4b0f8] Pluto v0.12.21

```

It’s 1.6 RC1 as RC2 is not yet available as a docker image. I get this:

```julia
arthur@767b47f0c62f:~$ julia --bug-report=rr
[ Info: Loading BugReporting package...
[FATAL /workspace/srcdir/rr/src/util.cc:1267:running_under_rr() errno: EPERM] Unexpected result for rrcall_check_presence: -1
=== Start rr backtrace:
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr(_ZN2rr13dump_rr_stackEv+0x28)[0x5a0fc8]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr(_ZN2rr15notifying_abortEv+0x47)[0x5a4e57]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr[0x5c9a12]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr(_ZN2rr16running_under_rrEb+0xb9)[0x5a1a69]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr[0x50caca]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr[0x50d8d9]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr[0x5c7028]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr(_ZN2rr17GdbCommandHandler16register_commandERNS_10GdbCommandE+0x2a)[0x4f45ca]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr[0x4bdf12]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr[0x4be006]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr[0x4c0e69]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr(__libc_csu_init+0x45)[0x727e75]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x7a)[0x7f7e3bccc02a]
/home/arthur/.julia/artifacts/24f3eb6277df1f22a6de3755306d033449697322/bin/rr[0x4c19ae]
=== End rr backtrace
[ Info: Preparing trace directory for upload (if your trace is large this may take a few minutes)

```

Rr is installed:

```julia
arthur@767b47f0c62f:~$ rr --version
rr version 5.4.0

```

Installing `BugReporting` seemed to work when run in Dockerfile, but not when I tried it just from the command line. I’ll put the stack trace as a comment as it’s rather long.

Note that the original poster on Slack cannot see your response here on Discourse. Consider _transcribing the appropriate answer back to Slack_, or pinging the poster here on Discourse so they can _follow this thread_.  
[(Original message :slack:)](https://julialang.slack.com/archives/C6A044SQH/p1615734031116600?thread_ts=1615734031.116600&cid=C6A044SQH) [(More Info)](https://github.com/JuliaCommunity/SlackBridge)

---

<div class="post-metadata">

**Author:** ![StatisticalMouse](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/statisticalmouse/32/43370_2.png) [@StatisticalMouse](https://discourse.julialang.org/u/StatisticalMouse)\
**Post date:** [March 14, 2021, 4:17pm UTC](https://discourse.julialang.org/t/problem-invoking-bug-report-rr-in-a-docker-image-i-have-the-following-package/57134/2 "2021-03-14T16:17:11Z")

</div>

The problem is as @Keno put it in Slack that `Docker filters unexpected syscalls. You can turn that off with privileged mode.`

Running Docker containers is a bad idea, for instance [Why A Privileged Container in Docker Is a Bad Idea](https://www.trendmicro.com/en_us/research/19/l/why-running-a-privileged-container-in-docker-is-a-bad-idea.html)

So it’s best not to do this.