You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am by no means a docker expert, so likely this is a user error on my end. I am able to successfully build the image using the quick setup in the README.md, having used both:
DOCKER_BUILDKIT=1 docker build . -t rosetta-helium:latest
and
But when attempting to run the image, I am met with error: [FATAL tini (7)] exec /app/start.sh failed: No such file or directory]. I've attempted to change the start.sh path entry point to /start.sh, ./start.sh to no avail. How would I remedy this issue? This fails in both wsl2 and powershell.
Here are my specs:
Docker Version:
Client: Docker Engine - Community
Cloud integration: v1.0.23
Version: 20.10.14
API version: 1.41
Go version: go1.16.15
Git commit: a224086
Built: Thu Mar 24 01:48:21 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Desktop
Engine:
Version: 20.10.14
API version: 1.41 (minimum version 1.12)
Go version: go1.16.15
Git commit: 87a90dc
Built: Thu Mar 24 01:46:14 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.5.11
GitCommit: 3df54a852345ae127d1fa3092b95168e4a88e2f8
runc:
Version: 1.0.3
GitCommit: v1.0.3-0-gf46b6ba
docker-init:
Version: 0.19.0
GitCommit: de40ad0
I am by no means a docker expert, so likely this is a user error on my end. I am able to successfully build the image using the quick setup in the README.md, having used both:
DOCKER_BUILDKIT=1 docker build . -t rosetta-helium:latest
and
DOCKER_BUILDKIT=1 docker build . -f Dockerfile_quick -t rosetta-helium:latest
I am attempting to run with the recommended command as well:
docker run -d --rm --init --ulimit "nofile=1000000:1000000" -v "$(pwd)/helium-data:/data" -p 8080:8080 -p 44158:44158 rosetta-helium:latest
But when attempting to run the image, I am met with error: [FATAL tini (7)] exec /app/start.sh failed: No such file or directory]. I've attempted to change the start.sh path entry point to /start.sh, ./start.sh to no avail. How would I remedy this issue? This fails in both wsl2 and powershell.
Here are my specs:
Docker Version:
Ubuntu:
The text was updated successfully, but these errors were encountered: