This repository was archived by the owner on Mar 27, 2025. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 21
[WE-145] Container deployment #60
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… avoid inconsistent staus of packages
… like the getting started
facchinm
approved these changes
Oct 9, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements support for basic container deployments on edge devices.
Supported platform are Ubuntu 16.04 on x86 devices, and debian like on ARM (read RaspberriPi)
Functionalities includes:
docker ps -aalsodocker psfor a single containerdocker runalso with private repo and.docker/config.jsonsupport for save credentialsdocker start/stop/renameof a containerdocker system prune -ato force the host system to be always clean when a container is deletedall these new functionalities are "end-to-end" tested via a test facility that is implemented with:
the new functionalities needs also to be linter compliant, but the compliancy will be addressed in another PR