The Dockerfile uses always the latest version of the offical provided alpine image. As alpine project can publishs new releases with potential backward incompatibilities, those can break that example.
So happened with current latest alpine, where "/sbin/init" fails since it's link destination "/sbin/openrc-init" is gone:
$ docker run -it -d --name=tedge tedge_docker_alpine
Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/sbin/init": stat /sbin/init: no such file or directory: unknown
Error: failed to start containers: tedge
Types of changes
What types of changes does your code introduce to thin-edge.io?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New example (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[ ] I have signed the CLA (in all commits with git commit -s)
[ ] I have added necessary documentation (if appropriate)
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Proposed changes
The Dockerfile uses always the latest version of the offical provided alpine image. As alpine project can publishs new releases with potential backward incompatibilities, those can break that example.
So happened with current latest alpine, where "/sbin/init" fails since it's link destination "/sbin/openrc-init" is gone:
Types of changes
What types of changes does your code introduce to
thin-edge.io? Put anxin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...