Crystal: dockerhub crystallang/crystal:0.19.2 does not ship with yaml

Created on 25 Sep 2016  Â·  3Comments  Â·  Source: crystal-lang/crystal

error while loading shared libraries: libyaml-0.so.2: cannot open shared object file: No such file or directory

is this by design ? ... can we have a nicer error message then ?
... if it's not by design ... any idea how to fix ?

feature infrastructure

Most helpful comment

Maybe docker images should come with everything the standard library uses...

All 3 comments

Maybe docker images should come with everything the standard library uses...

sounds reasonable to me ...

On Sun, Sep 25, 2016 at 4:00 AM, Ary Borenszweig [email protected]
wrote:

Maybe docker images should come with everything the standard library
uses...

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/crystal-lang/crystal/issues/3347#issuecomment-249415407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAsZzFxa7Q8kax-raegwaLj2D-XpAxWks5qtlRQgaJpZM4KFzUk
.

Hello,

This has been solved by #3441:

$ docker run -it crystallang/crystal bash

root@a873bceeab61:/opt/crystal# crystal --version
Crystal 0.20.3 [b1416e2] (2016-12-23)

root@a873bceeab61:/opt/crystal# cd /tmp/

root@a873bceeab61:/tmp# cat test.cr 
require "yaml"

puts YAML.dump({:foo => 10})

root@a873bceeab61:/tmp# crystal build test.cr

root@a873bceeab61:/tmp# ./test 
---
foo: 10

root@a873bceeab61:/tmp# ldd test
    linux-vdso.so.1 =>  (0x00007fffe47d3000)
    libyaml-0.so.2 => /usr/lib/x86_64-linux-gnu/libyaml-0.so.2 (0x00007f7997a2e000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7997810000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f7997607000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7997403000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f79971ed000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7996e27000)
    /lib64/ld-linux-x86-64.so.2 (0x000055e19d47d000)

Cheers!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

will picture will  Â·  3Comments

Sija picture Sija  Â·  3Comments

RX14 picture RX14  Â·  3Comments

lbguilherme picture lbguilherme  Â·  3Comments

paulcsmith picture paulcsmith  Â·  3Comments