Re: Differences between /proc/config.gz and developer container's configuration

Hi, Yes, this is expected. The kernel build process was changed a few releases ago to build in two phases: first the modules, then the kernel itself. The initramfs image is built during the second phase where it can include the pre-built modules, and that is where the config option now gets s

Re: Install OpenSSH 7.3 on CoreOS

On Tuesday, October 18, 2016 at 1:51:08 PM UTC-7, Solito Reyes III wrote: > > I need to upgrade OpenSSH to 7.3. What are the best steps to go about > this on my CoreOS system? > The easier route will most likely be to mask the CoreOS sshd units, and run the specific version you want in a contai

Re: modular cloud config

Hi, I don't believe that is supported by cloud-config. Ignition, the successor to cloud-config, does support it. You can use ignition.config.append as described at the following URL to include a list of files: https://coreos.com/ignition/docs/latest/configuration.html Thanks. David On Wed

Boot failures with recent Container Linux alpha

The recent alpha release of Container Linux v1312.0.0 incorrectly generated disk images without embedding a verity checksum. While this version's deployment was halted quickly and replaced with the fixed version v1313.0.0, a few machines have automatically installed v1312.0.0 and may be experienci

Re: Building CoreOS kernel

On Tue, Feb 14, 2017 at 1:46 PM, 'Matt Mathis' via CoreOS Dev wrote: > I am trying to inject custom kernel code into CoreOS, to add experimental > instrumentation to TCP. This can not be done in a module: it requires > changes to the resident part of TCP. > > I am having difficulty connecting the

Re: Building CoreOS kernel

On Tue, Feb 14, 2017 at 2:42 PM, 'Matt Mathis' via CoreOS Dev wrote: > Thank you! > > Does COREOS_SOURCE_REVISION need to be monotonic (within the kernel > version), or just not match any recently cached versions? If I never plan > to build a stock kernel, is it risky to stomp on future versions

Re: How to add new tests to mantle/kola

On Thu, Mar 2, 2017 at 12:25 PM, Marshall Onsrud wrote: > > How do I add/register a new test within mantle/kola framework. See kola/registry/registry.go. Also run "cros_workon --host start mantle" so you can emerge your modified version from the third_party repo, unless you just want to build it

Re: Writing/Editing Kola Tests within Chroot

On Fri, Mar 3, 2017 at 10:53 AM, Marshall Onsrud wrote: > > If I enter my CoreOS chrooted enviroment to kola run unit tests is there any > way I can edit/change tests within the chroot and re-run them with new > changes? Run the command I sent last time, "cros_workon --host start mantle". Then wh

Re: What user account do kola tests use?

On Fri, Mar 10, 2017 at 1:40 PM, Marshall Onsrud wrote: > > Which user account do the kola tests use? They use "core", and a new SSH key is generated and injected into your test's user data for that user. You could try using ./set_shared_user_password.sh in the SDK to build an image with a defau

Re: CoreOS build failing due to circular dependencies

On Tue, Mar 14, 2017 at 2:03 PM, 'Matt Mathis' via CoreOS Dev wrote: >> (sys-fs/cryptsetup-1.7.2:0/0::portage-stable, ebuild scheduled for merge >> to '/build/amd64-usr/') depends on >> (sys-fs/lvm2-2.02.145-r3:0/0::coreos, ebuild scheduled for merge to >> '/build/amd64-usr/') (buildtime) >> (s

Re: Is there a way to pin CoreOS and constituent ebuild versions?

On Mon, Apr 10, 2017 at 4:32 PM, 'Matt Mathis' via CoreOS Dev wrote: > I have been having recurrent build problem due to version/dependency skew at > the CoreOS head. I don't need to continuously track the bleeding edge. > Is there a way for me to pin CoreOS and all constituent ebuilds to know

Re: Is there a way to pin CoreOS and constituent ebuild versions?

tters of life and death, because for some users, they are. > > On Mon, Apr 10, 2017 at 4:46 PM, David Michael > wrote: >> >> On Mon, Apr 10, 2017 at 4:32 PM, 'Matt Mathis' via CoreOS Dev >> wrote: >> > I have been having recurrent build problem d

Re: Adding new ebuild to package

On Sun, Apr 23, 2017 at 1:38 PM, Charles Allen wrote: > I looked at the following websites: > > https://coreos.com/os/docs/latest/sdk-modifying-coreos.html > https://coreos.com/os/docs/latest/sdk-tips-and-tricks.html#add-new-upstream-package > > But when I get to where I have the new ebuild under

Re: PRs and Copyright

On Wed, Apr 26, 2017 at 1:30 PM, Brandon Philips wrote: > I haven't seen this before; generally all of our projects have Copyright > "The XYZ" authors: > https://github.com/coreos/etcd/blob/master/proxy/httpproxy/director.go#L1 > > If it is in the commit message I think it is OK but as you aren't

Re: auto resize of root partition

On Thu, Apr 27, 2017 at 5:02 AM, Christopher Schmidt wrote: > Hi, > > obviously CoreOS does resize the root partition to fill the disk on the next > boot. > > Is there a way to disable that? Can you just mask extend-filesystems.service with Ignition? Thanks. David

Re: Build kernel modules

On Tue, Jan 16, 2018 at 7:56 AM, enexis wrote: > Hi all, > > I was trying to build new kernel module (what is missing in the current > releases) following this guide: > https://coreos.com/os/docs/latest/kernel-modules.html > > All good except the fact when I start the container with nspawn there i

Re: Build kernel modules

On Tue, Jan 16, 2018 at 11:56 AM, enexis wrote: > On Tuesday, January 16, 2018 at 5:06:27 PM UTC+2, David Michael wrote: >> On Tue, Jan 16, 2018 at 7:56 AM, enexis wrote: >> > Hi all, >> > >> > I was trying to build new kernel module (what is missing in the c

Re: inode size for coreos, ext4 is set to 128 than default 256. Reqeusting explanation

On Tue, Feb 20, 2018 at 11:43 AM, Himanshu Khurana wrote: > tune2fs -l /dev/xvda9 > Inode size: 128 > > while as per /etc/mke2fs.conf > > } > ext4 = { > features = > has_journal,extent,huge_file,flex_bg,uninit_bg,64bit,dir_nlink,extra_isize > inode_size = 256

Re: ZFS Support in CoreOS

On Thu, Apr 12, 2018 at 10:28 AM, Nick wrote: > Hopefully this is the right place to ask... > > Are there any plans to include ZFS support out-of-the-box? No drivers will be included that aren't part of the mainline kernel. > Are there any official or recommended guides on setting up ZFS on Core

Re: ZFS Support in CoreOS

at example doesn't install the userspace components, but I think one of the forks expanded it to do so. Thanks. David > Thanks, > > Nick > > On Friday, 13 April 2018 01:00:57 UTC+10, David Michael wrote: >> >> On Thu, Apr 12, 2018 at 10:28 AM, Nick wrote: >&

Re: Using CoreOS with AMD GPU

On Thu, May 24, 2018 at 11:55 AM, Kenny Ho wrote: > I am interested in using CoreOS with AMD GPU. Is this something that can be > done with some post-install SDK on a standard CoreOS or do I need to make > patches to the regular CoreOS distribution itself? GPU drivers are not being built, so you

Re: Install additional packages in CoreOS SDK

On Wed, Aug 15, 2018 at 5:49 PM, Adam Jenkins wrote: > I have been able to create a chroot using the CoreOS SDK and create my own > image, but I'm not sure how to actually install additional dependencies. > Any help would be greatly appreciated. If you're using the build_image script to create a

Re: Install additional packages in CoreOS SDK

On Wed, Aug 15, 2018 at 7:01 PM, Adam Jenkins wrote: > Thanks David. Do you know how I might go about adding files to the image? You could either package them and add the package to coreos-base/coreos, or edit the scripts to write them. If your goal is just to add miscellaneous files, you might

Re: How to boot CoreOS with customized Ignition?

On Mon, Sep 10, 2018 at 4:18 AM, Yifang WANG wrote: > For testing purposes, I'd like to add new OEM support in Ignition source > code and build new CoreOS image via CoreOS SDK (cork create, cork enter, etc > ). > I understand that Ignition runs in initramfs, and also find kernel parameter > CONFIG

Re: Compiling CoreOS's GRUB under Ubuntu

On Wed, Jun 20, 2018 at 10:29 AM Artem Leshchev wrote: > среда, 20 июня 2018 г., 17:20:26 UTC+3 пользователь David Michael написал: >> Okay, thanks for sending the configure line. I ran the test with the >> pc platform, which passes reliably, but I do see the failure with efi.

Re: An encrypted coreos overlay file sytem using tpm2.0

On Tue, Nov 13, 2018 at 10:16 AM Daniel McAllister wrote: > > Hello All, > > I am developing on something that I call "An encrypted overlay file system > with tpm2.0" for coreos. The feature is basically a new dracut module which > will mount a new file system on top of the normal file system as

Re: fgets crashes in coreos machine

On Fri, Nov 16, 2018 at 1:19 AM Simran Bindra wrote: > > I have this C code snippet which runs on a coreOS machine: > > - > char db[512]; > snprintf(db, 512, "%s %s", , ); > FILE* pipe = popen(db, "

Re: sdk build failures with cargo since v1967.0.0

On Tue, Dec 18, 2018 at 5:14 PM Dongsu Park wrote: > > Hi, I'm maintainer of Flatcar Linux . > I'm aware that it's coreos-dev list. Though since Flatcar Linux is > a fork of Container Linux, I'm pretty sure some of you could have > some idea about my issue. > > Recently

Re: sdk build failures with cargo since v1967.0.0

On Tue, Dec 18, 2018 at 7:28 PM David Michael wrote: > On Tue, Dec 18, 2018 at 5:14 PM Dongsu Park wrote: > > > > Hi, I'm maintainer of Flatcar Linux <https://flatcar-linux.org>. > > I'm aware that it's coreos-dev list. Though since Flatcar Linux is >

Re: Privilege TCP Ports

On Tue, Feb 19, 2019 at 1:17 PM Mark Madlangbayan wrote: > I have a java-based docker container hosted on CoreOS 4.14.96-coreos-r1 just > using systemd running us the core user. I'm having a hard time making it to > work with ports lower than 1024. I'm specifically trying to use TCP 443. On

Re: .la files are removed

On Wed, Mar 13, 2019 at 5:23 PM wrote: > On Wednesday, March 13, 2019 at 6:44:05 PM UTC+2, Andrew Jeddeloh wrote: >> Try using >> >> equery-amd64-usr f | grep '.la' > > .la files ar not there. > >> to see if the .la files are in the package to begin with. If they're >> not, check the use flags (e

New Container Linux release signing subkey

Container Linux release images will be signed with a new key due to scheduled subkey rotation in all channels, starting with the alpha release in two weeks (May 7). With today's promotion of version 2079.3.0 to stable, the tools shipped with Container Linux in all channels support the new subkey.

Re: Version bump of runc on stable branch

On Mon, May 20, 2019 at 2:14 PM Ron Gutierrez wrote: > Hi, > > We need to run an upgraded version of runc to pickup a bug fix related to a > race condition that occurs under heavy load. This bug fix was included in the > runc 1.0-rc7 release. This release also contained the runc vulnerability >

Re: Version bump of runc on stable branch

On Mon, May 20, 2019 at 3:11 PM Ron Gutierrez wrote: > Thanks for the response! > > Yea, you are right about the runc and docker versions. I made a mistake in > the way I interpreted this PR to docker > (https://github.com/docker/engine/commit/cbe11bdc6da871bdce0993fddb4ff8a29c476a63) > and was