From: whiteman808 <whiteman808@paraboletancza.org>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Choosing the right profile for Gentoo LXC/Docker containers
Date: Sun, 8 Dec 2024 13:43:41 +0100 [thread overview]
Message-ID: <s6v23oqol5cwoz4vkes5xpz73j65rhtaolu7kfpj5lxcxpqnal@eegh6zxfg74x> (raw)
Hey,
I'm going to setup Gentoo binary package server for LXC and Docker
containers that will be used on the production server.
On the server I already have hardened profile, so the my question is
whether using hardened profile on the containers will be beneficial in
terms of security or if it is sufficient to leave normal default Gentoo
profile default/linux/amd64/23.0/systemd.
I'll use these containers both for testing locally development
applications on my laptop before deploying them, and also on the
production server.
I use this server mainly for hosting my own personal stuff like PHP
websites, mailing lists, Jabber server, Git repositories.
I want these containers to be easily deployable on different
environments, and portable so I should set in CFLAGS, CXXFLAGS etc. -O2
-pipe, without -march=..., right?
Thank you in advance for helpful answers,
whiteman808.
reply other threads:[~2024-12-08 12:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s6v23oqol5cwoz4vkes5xpz73j65rhtaolu7kfpj5lxcxpqnal@eegh6zxfg74x \
--to=whiteman808@paraboletancza.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox