maxmcd/deno-docker

Dockerfiles for Deno

Archived

This has been superseeded by better run and better maintained deno docker projects. I recommend using https://github.com/hayd/deno-docker and the corresponding: https://hub.docker.com/r/hayd/deno

Old readme below:

---

Deno Docker

Docker images for denoland/deno

Tags:

• jessie (0/jessie/Dockerfile)
• slim (0/slim/Dockerfile)

Contributing

Issues and pull requests are welcome.

deno-docker's Issues

The default command should silent compiling notifications

If a silent/quiet flag is added (denoland/deno#3162), the default command should utilize it.

Issue when running deno on a machine with 1 CPU

I'm having issues running Deno in this image, specifically when running in a container on an Ubuntu server. I'm a little out of my depth here so I appreciate this may not be an issue with you package, but perhaps you can still help.

Running locally on MacOS the image runs as expected.

MacOS: 10.14.4 (18E226)
Docker version 18.09.2, build 6247962

When attempting to run any file with Deno inside the image on an Ubuntu machine Deno just ends up hanging.

> docker run -it maxmcd/deno:latest bash
root@eedc4941409a:/# deno --version
deno: 0.3.7
v8: 7.4.238
typescript: 3.4.1
root@eedc4941409a:/# echo "console.log('foo')" > foo.ts
root@eedc4941409a:/# deno -AD ./foo.ts
DEBUG RS - mkdir -p /root/.cache/deno/gen
DEBUG RS - set dir perm to 493
DEBUG RS - mkdir -p /root/.cache/deno/deps
DEBUG RS - set dir perm to 493
DEBUG RS - mkdir -p /root/.cache/deno/deps/http
DEBUG RS - set dir perm to 493
DEBUG RS - mkdir -p /root/.cache/deno/deps/https
DEBUG RS - set dir perm to 493
DEBUG RS - root /root/.cache/deno
DEBUG RS - gen /root/.cache/deno/gen
DEBUG RS - deps /root/.cache/deno/deps
DEBUG RS - deps_http /root/.cache/deno/deps/http
DEBUG RS - deps_https /root/.cache/deno/deps/https
DEBUG RS - Deno isolate init with snapshots.
DEBUG RS - resolve_module specifier ./foo.ts referrer .
DEBUG RS - msg_from_js Start sync true
DEBUG JS - cwd /
DEBUG JS - args [ "./foo.ts" ]
DEBUG RS - resolve_module specifier ./foo.ts referrer .
DEBUG RS - main_module file:///foo.ts
DEBUG RS - fetch_module_meta_data. specifier file:///foo.ts referrer .
DEBUG RS - resolve_module specifier file:///foo.ts referrer .
DEBUG RS - module_name: file:///foo.ts, filename: /foo.ts
DEBUG RS - fetch local or reload file:///foo.ts is_module_remote false
DEBUG RS - found local source

After this it hangs indefinitely.

Ubuntu 18.04.2 LTS (Bionic Beaver)
Docker version 18.09.5, build e8ff056

Any tips would be appreciated.

Automatically build new deno versions and push version tagged images to hub

I don't know version of deno in your docker util pull down.
So is there possibilty that use such like dependencies.io.
Once deno release -> notify deno-docker -> run travis -> update readme -> release docker with version in tag

deno cannot run in slim version

first, deno cannot find, so I use ldd to see errors

Error loading shared library libstdc++.so.6: No such file or directory (needed by deno)
	libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7fd015ac1000)
Error loading shared library libgcc_s.so.1: No such file or directory (needed by deno)
	libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7fd015ac1000)
Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by deno)

so I run this:

apk add libc6-compat
apk add libstdc++

But it goes like this, I cannot resolve it
tried sgerrand/alpine-pkg-glibc failed

> ldd deno
	/lib64/ld-linux-x86-64.so.2 (0x7f993e800000)
	libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7f993e800000)
	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7f993e4ae000)
	libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f993e800000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f993e29c000)
	libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f993e800000)
Error relocating deno: backtrace: symbol not found
Error relocating deno: backtrace_symbols: symbol not found

[QUESTION] Using the master build setup as a development docker

This is cool initiative. Thanks for that.

I actually realize that this is already there while I actually wrote the whole thing myself 😄

I am going to use this instead, now, is your intention to have the source copied into $GOPATH and built into it into the docker is to somehow create a "shared folder" using -v option around that ?

Basically how will you use the same setup for development? I am trying to use shared folders and making the docker slim here, but this seems to be taking a different approach. Just wanted to know.

Thanks in advance.

deno2

hope support branch choose