Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
TASTE
taste-setup
Commits
899b8712
Commit
899b8712
authored
Oct 23, 2017
by
Thanassis Tsiodras
Browse files
Update installation instructions, now that the Dockerfile is officially announced.
parent
9c90e96e
Changes
1
Hide whitespace changes
Inline
Side-by-side
README.md
View file @
899b8712
...
...
@@ -4,19 +4,52 @@ TASTE
This is the meta package that is used to install all git modules required
to make a TASTE installation.
If possible, please use the TASTE VM - available at http://taste.tools
Installation
============
TASTE Virtual Machine
---------------------
If possible, please use the TASTE VM - it is available at
[
http://taste.tools
](
http://taste.tools
)
(follow the 'Downloads' link and download the .ova file - that's a VirtualBox
machine that you can import via VirtualBox's "File/Import Appliance")
machine that you can import via VirtualBox's
*"File/Import Appliance"*
).
Docker container
----------------
The repository includes a Dockerfile, that creates a fully functional "taste" Docker image,
built from the sources necessary in all the submodules.
Simply Process this Dockerfile with:
docker build -t taste .
And we then recommend to launch a fresh TASTE container with proper X11 redirection setup, with...
Otherwise, use a Debian-based distribution, create a new 'taste' user, and...
./Docker-run.sh
This script does all the necessary setup to map your local X11 socket inside the container,
allowing you to use X11 applications. In addition, your
`$HOME`
folder is mapped inside the
container under the
`/root/work`
folder, so any work you do in there will survive the
container's eventual closing. As with all Docker containers, you can also commit the
changes you perform in your container (via
`docker commit...`
) and create your own
customized images.
For users where the TASTE VM is a concern for reasons of security
*
(e.g. uncertainty of what
exactly is included inside it)
*
the Docker container is a complete and clear answer:
it is built from source, so there is full visibility on what is inside it.
In Debian-based distributions
-----------------------------
In theory, under a modern Debian-based distribution a native install is also possible:
you would start by creating a new 'taste' user, and...
$ git clone https://gitrepos.estec.esa.int/taste/taste-setup.git tool-src
$ cd tool-src
$ ./Update-TASTE.sh
Then
follow the prompts to fix whatever issues are detected in your configuration.
You'd then have to
follow the prompts to fix whatever issues are detected in your configuration.
The setup depends on the environment being a Debian distro; if this is not the case,
Since the installation scripts depend on Debian tools, this kind of setup can only work inside
environments that are (or are based on) a Debian distribution; if this is not the case,
you can try the setup from inside a debootstrap-ed chroot:
# mkdir /opt/stretch-chroot
...
...
@@ -26,6 +59,3 @@ you can try the setup from inside a debootstrap-ed chroot:
# mount -o bind /dev /opt/stretch-chroot/dev/
# mount -o bind /dev/pts /opt/stretch-chroot/dev/pts/
# chroot /opt/stretch-chroot
There is also a Dockerfile (currently under construction) that will eventually
automate the setup enough to allow working under any distribution.
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment