Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for nerdctl #38

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from
Draft

Support for nerdctl #38

wants to merge 7 commits into from

Conversation

kdambekalns
Copy link
Member

This makes beach support nerdctl for use with a containerd setup, like Rancher Desktop.

@kdambekalns kdambekalns self-assigned this Feb 4, 2022
@kdambekalns
Copy link
Member Author

In the end this should be able to use both, docker and nerdctl, depending on the user setup.

And it is not finished yet:

  • relies on docker.sock for the nginx proxy
  • user/group for the database container need to be set
  • some unused flags are still used (e.g. -force during beach down)

@kdambekalns
Copy link
Member Author

As of now:

$ beach start
INFO Starting reverse proxy and database server ...
INFO[0000] Creating network local_beach
INFO[0000] Creating network LocalBeach_default
WARN[0000] Ignoring: volume: Bind: [CreateHostPath]
WARN[0000] Ignoring: volume: Bind: [CreateHostPath]
WARN[0000] Ignoring: service database: [HealthCheck]
WARN[0000] Ignoring: volume: Bind: [CreateHostPath]
INFO[0000] Ensuring image flownative/localbeach-nginx-proxy:0.3.0
INFO[0000] Ensuring image mariadb:10.5
INFO[0000] Creating container local_beach_database
INFO[0000] Creating container local_beach_nginx
FATA[0000] failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:75: mounting "/var/run/docker.sock" to rootfs at "/tmp/docker.sock" caused: stat /var/run/docker.sock: no such file or directory: unknown
FATA[0000] error while creating container local_beach_nginx: exit status 1
FATAL container startup failed

$ beach down
INFO Stopping reverse proxy and database server ...

For the database and nginx proxy, use compose.yaml - since it's not
specifically docker, that makes sense. And according to the spec,
that is the preferred name.

https://github.com/compose-spec/compose-spec/blob/master/spec.md#compose-file
The "compose rm" command is not implemented… "compose down" does the
same thing.
The (autogenerated) project name ".LocalBeach" is invalid, so pass
"LocalBeach" using a CLI parameter.

The "name" top-level element from the compose spec is not supported,
it seems, otherwise it would have been a better solution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant