home.social

#apko — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #apko, aggregated by home.social.

  1. What I did in the last couple of weeks (part 8):

    Did I mention previously that building container images with apko using packages from WolfiOS, is a very pleasant and nice experience?

    Well, I needed to build an image in GitlabCI. For GitHub, there is an official apko action that works flawlessly.
    For GitlabCI though I encountered that the official apko image is not working due to the lack of a shell inside the container (which normally is a good things safety-wise).

    So, I built my own apko image on GitHub and then used that in the GitlabCI to build an image using apko there.

    github.com/kastl-ars/wolfi-apk

    I also opened an issue with the apko maintainers for this, as GitlabCI support would be really nice.

    BTW, huge shoutout to the Chainguard folks for maintaining WolfiOS and so many safe and small images!

    #container #GitlabCI #cicd #apko #chainguard #

  2. What I did in the last couple of weeks (part 8):

    Did I mention previously that building container images with apko using packages from WolfiOS, is a very pleasant and nice experience?

    Well, I needed to build an image in GitlabCI. For GitHub, there is an official apko action that works flawlessly.
    For GitlabCI though I encountered that the official apko image is not working due to the lack of a shell inside the container (which normally is a good things safety-wise).

    So, I built my own apko image on GitHub and then used that in the GitlabCI to build an image using apko there.

    github.com/kastl-ars/wolfi-apk

    I also opened an issue with the apko maintainers for this, as GitlabCI support would be really nice.

    BTW, huge shoutout to the Chainguard folks for maintaining WolfiOS and so many safe and small images!

    #container #GitlabCI #cicd #apko #chainguard #

  3. What I did in the last couple of weeks (part 8):

    Did I mention previously that building container images with apko using packages from WolfiOS, is a very pleasant and nice experience?

    Well, I needed to build an image in GitlabCI. For GitHub, there is an official apko action that works flawlessly.
    For GitlabCI though I encountered that the official apko image is not working due to the lack of a shell inside the container (which normally is a good things safety-wise).

    So, I built my own apko image on GitHub and then used that in the GitlabCI to build an image using apko there.

    github.com/kastl-ars/wolfi-apk

    I also opened an issue with the apko maintainers for this, as GitlabCI support would be really nice.

    BTW, huge shoutout to the Chainguard folks for maintaining WolfiOS and so many safe and small images!

    #container #GitlabCI #cicd #apko #chainguard #

  4. What I did in the last couple of weeks (part 8):

    Did I mention previously that building container images with apko using packages from WolfiOS, is a very pleasant and nice experience?

    Well, I needed to build an image in GitlabCI. For GitHub, there is an official apko action that works flawlessly.
    For GitlabCI though I encountered that the official apko image is not working due to the lack of a shell inside the container (which normally is a good things safety-wise).

    So, I built my own apko image on GitHub and then used that in the GitlabCI to build an image using apko there.

    github.com/kastl-ars/wolfi-apk

    I also opened an issue with the apko maintainers for this, as GitlabCI support would be really nice.

    BTW, huge shoutout to the Chainguard folks for maintaining WolfiOS and so many safe and small images!

    #container #GitlabCI #cicd #apko #chainguard #

  5. What I did in the last couple of weeks (part 8):

    Did I mention previously that building container images with apko using packages from WolfiOS, is a very pleasant and nice experience?

    Well, I needed to build an image in GitlabCI. For GitHub, there is an official apko action that works flawlessly.
    For GitlabCI though I encountered that the official apko image is not working due to the lack of a shell inside the container (which normally is a good things safety-wise).

    So, I built my own apko image on GitHub and then used that in the GitlabCI to build an image using apko there.

    github.com/kastl-ars/wolfi-apk

    I also opened an issue with the apko maintainers for this, as GitlabCI support would be really nice.

    BTW, huge shoutout to the Chainguard folks for maintaining WolfiOS and so many safe and small images!

    #container #GitlabCI #cicd #apko #chainguard #

  6. This week I have been building some #container images for e.g. #renovatebot and I must say I really dig #Chainguard and the #WolfiOS ecosystem. Building an image locally using #apko was a breeze. Building on #GitHub was easy due to their Github Action.

    And the long list of packages available is nice.

    And the list of CVEs in the image is really short.

    I'll try to get my hands dirty with melange and try to build a Pluto package for WolfiOS...

  7. This week I have been building some #container images for e.g. #renovatebot and I must say I really dig #Chainguard and the #WolfiOS ecosystem. Building an image locally using #apko was a breeze. Building on #GitHub was easy due to their Github Action.

    And the long list of packages available is nice.

    And the list of CVEs in the image is really short.

    I'll try to get my hands dirty with melange and try to build a Pluto package for WolfiOS...

  8. This week I have been building some #container images for e.g. #renovatebot and I must say I really dig #Chainguard and the #WolfiOS ecosystem. Building an image locally using #apko was a breeze. Building on #GitHub was easy due to their Github Action.

    And the long list of packages available is nice.

    And the list of CVEs in the image is really short.

    I'll try to get my hands dirty with melange and try to build a Pluto package for WolfiOS...

  9. This week I have been building some #container images for e.g. #renovatebot and I must say I really dig #Chainguard and the #WolfiOS ecosystem. Building an image locally using #apko was a breeze. Building on #GitHub was easy due to their Github Action.

    And the long list of packages available is nice.

    And the list of CVEs in the image is really short.

    I'll try to get my hands dirty with melange and try to build a Pluto package for WolfiOS...

  10. This week I have been building some #container images for e.g. #renovatebot and I must say I really dig #Chainguard and the #WolfiOS ecosystem. Building an image locally using #apko was a breeze. Building on #GitHub was easy due to their Github Action.

    And the long list of packages available is nice.

    And the list of CVEs in the image is really short.

    I'll try to get my hands dirty with melange and try to build a Pluto package for WolfiOS...

  11. as a reminder, if you are using #apko to build @alpinelinux 3.18 based images, you will need 0.8.0 or later which adds support for the python~3.11 type of dependency relationships.

  12. as a reminder, if you are using #apko to build @alpinelinux 3.18 based images, you will need 0.8.0 or later which adds support for the python~3.11 type of dependency relationships.

  13. as a reminder, if you are using #apko to build @alpinelinux 3.18 based images, you will need 0.8.0 or later which adds support for the python~3.11 type of dependency relationships.

  14. as a reminder, if you are using #apko to build @alpinelinux 3.18 based images, you will need 0.8.0 or later which adds support for the python~3.11 type of dependency relationships.

  15. as a reminder, if you are using #apko to build @alpinelinux 3.18 based images, you will need 0.8.0 or later which adds support for the python~3.11 type of dependency relationships.

  16. #apko 0.8.0 has been released, adding support for the tilde version matching operator (oops, we forgot about it, sorry), as used by alpine 3.18's python packages.

  17. #apko 0.8.0 has been released, adding support for the tilde version matching operator (oops, we forgot about it, sorry), as used by alpine 3.18's python packages.

  18. #apko 0.8.0 has been released, adding support for the tilde version matching operator (oops, we forgot about it, sorry), as used by alpine 3.18's python packages.

  19. #apko 0.8.0 has been released, adding support for the tilde version matching operator (oops, we forgot about it, sorry), as used by alpine 3.18's python packages.

  20. #apko 0.8.0 has been released, adding support for the tilde version matching operator (oops, we forgot about it, sorry), as used by alpine 3.18's python packages.

  21. #melange 0.3.0 has been released, with a lot of improvements from the community!

    if you didn't know, #melange is the declarative APK builder based on #apko which allows building packages for any APK distribution (such as @alpinelinux, @wolfi or @AdelieLinux) using a composable pipeline built from declarative components.

    @wolfi is built with #melange, the repository being a forest of declarative YAML-based package definitions.

  22. #melange 0.3.0 has been released, with a lot of improvements from the community!

    if you didn't know, #melange is the declarative APK builder based on #apko which allows building packages for any APK distribution (such as @alpinelinux, @wolfi or @AdelieLinux) using a composable pipeline built from declarative components.

    @wolfi is built with #melange, the repository being a forest of declarative YAML-based package definitions.

  23. #melange 0.3.0 has been released, with a lot of improvements from the community!

    if you didn't know, #melange is the declarative APK builder based on #apko which allows building packages for any APK distribution (such as @alpinelinux, @wolfi or @AdelieLinux) using a composable pipeline built from declarative components.

    @wolfi is built with #melange, the repository being a forest of declarative YAML-based package definitions.

  24. #melange 0.3.0 has been released, with a lot of improvements from the community!

    if you didn't know, #melange is the declarative APK builder based on #apko which allows building packages for any APK distribution (such as @alpinelinux, @wolfi or @AdelieLinux) using a composable pipeline built from declarative components.

    @wolfi is built with #melange, the repository being a forest of declarative YAML-based package definitions.

  25. #melange 0.3.0 has been released, with a lot of improvements from the community!

    if you didn't know, #melange is the declarative APK builder based on #apko which allows building packages for any APK distribution (such as @alpinelinux, @wolfi or @AdelieLinux) using a composable pipeline built from declarative components.

    @wolfi is built with #melange, the repository being a forest of declarative YAML-based package definitions.

  26. #apko 0.7.3 is released, with some minor bugfixes, largely relating to the use of apko on case-insensitive filesystems.

  27. #apko 0.7.3 is released, with some minor bugfixes, largely relating to the use of apko on case-insensitive filesystems.

  28. #apko 0.7.3 is released, with some minor bugfixes, largely relating to the use of apko on case-insensitive filesystems.

  29. #apko 0.7.3 is released, with some minor bugfixes, largely relating to the use of apko on case-insensitive filesystems.

  30. #apko 0.7.3 is released, with some minor bugfixes, largely relating to the use of apko on case-insensitive filesystems.

  31. #apko 0.7.0 is released 🎉

    new release, exactly on the 1 year mark of the first apko release!

    this brings an entirely new reimplementation of apk-tools as a reusable #golang package, and a cross-platform VFS implementation.

    the result: you can compose alpine and wolfi images on non-Linux machines, such as macOS and freebsd. it might also work on windows, but we haven't tested it.

  32. #apko 0.7.0 is released 🎉

    new release, exactly on the 1 year mark of the first apko release!

    this brings an entirely new reimplementation of apk-tools as a reusable #golang package, and a cross-platform VFS implementation.

    the result: you can compose alpine and wolfi images on non-Linux machines, such as macOS and freebsd. it might also work on windows, but we haven't tested it.

  33. #apko 0.7.0 is released 🎉

    new release, exactly on the 1 year mark of the first apko release!

    this brings an entirely new reimplementation of apk-tools as a reusable #golang package, and a cross-platform VFS implementation.

    the result: you can compose alpine and wolfi images on non-Linux machines, such as macOS and freebsd. it might also work on windows, but we haven't tested it.

  34. #apko 0.7.0 is released 🎉

    new release, exactly on the 1 year mark of the first apko release!

    this brings an entirely new reimplementation of apk-tools as a reusable #golang package, and a cross-platform VFS implementation.

    the result: you can compose alpine and wolfi images on non-Linux machines, such as macOS and freebsd. it might also work on windows, but we haven't tested it.

  35. #apko 0.7.0 is released 🎉

    new release, exactly on the 1 year mark of the first apko release!

    this brings an entirely new reimplementation of apk-tools as a reusable #golang package, and a cross-platform VFS implementation.

    the result: you can compose alpine and wolfi images on non-Linux machines, such as macOS and freebsd. it might also work on windows, but we haven't tested it.