sadaszewski / focker Goto Github PK

... of just stopping them at the beginning of compose build.

Thanks for this project.
My first post on the forums, one year ago, was about this very thing.

Perhaps you could add a short list or roadmap of what needs help.
Haven't sat down to use this yet.

Are there any plans to integrate focker with any of the existing container runtimes? From what I know many people hope for kubernetes support on FreeBSD so focker would need to integrate with one of the existing container runtimes that are supported by kubernetes already unless someone wants to create yet another container runtime.

From the kubernetes docs currently supported container runtimes are:

• docker
• CRI-O
• containerd
• frakti

https://kubernetes.io/docs/setup/production-environment/container-runtimes/

Error:

focker bootstrap
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.7/site-packages/focker/focker.py", line 211, in <module>
    main()
  File "/usr/local/lib/python3.7/site-packages/focker/focker.py", line 200, in main
    zfs_init()
  File "/usr/local/lib/python3.7/site-packages/focker/zfs.py", line 193, in zfs_init
    poolname = zfs_poolname()
  File "/usr/local/lib/python3.7/site-packages/focker/zfs.py", line 185, in zfs_poolname
    poolname = zfs_parse_output(['zfs', 'list', '-H', '/'])
  File "/usr/local/lib/python3.7/site-packages/focker/zfs.py", line 26, in zfs_parse_output
    out = zfs_run(command)
  File "/usr/local/lib/python3.7/site-packages/focker/zfs.py", line 21, in zfs_run
    out = subprocess.check_output(command, stderr=subprocess.STDOUT)
  File "/usr/local/lib/python3.7/subprocess.py", line 411, in check_output
    **kwargs).stdout
  File "/usr/local/lib/python3.7/subprocess.py", line 512, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['zfs', 'list', '-H', '/']' returned non-zero exit status 1.

I have a zfs pool/dataset in /data (not /) I suppose that's why this fails, but I couldn't figure how to tell focker to look in /data

in fact, I get this error even when not passing any arg

Facilitate bootstrap of different FreeBSD version

need to optimize by providing cache to the datasets obtained from listings

While looking to fetch the GitHub sources for 0.91 (See #1), I noticed the 0.92 git tag. The current focker PyPI (sdist) version is 0.91.

It would be create, if 0.92 is 'complete', to update the PyPI sdist to 0.92, from the revision at which that version was tagged

sudo focker compose r focker-compose.yml clone Waiting for /var/lock/focker.lock ... Lock acquired. poolname: zroot Traceback (most recent call last): File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/local/lib/python3.7/site-packages/focker/focker.py", line 266, in <module> main() File "/usr/local/lib/python3.7/site-packages/focker/focker.py", line 262, in main args.func(args) File "/usr/local/lib/python3.7/site-packages/focker/compose.py", line 199, in command_compose_run raise NotImplemented

Am Im missing something?
i followed the guide here?
https://github.com/sadaszewski/focker#commands
and https://github.com/sadaszewski/focker#focker-composeyml-syntax

Allow to include files inside of Fockerfile

PyPI is currently at 0.91 but there isn't a corresponding git tag for this version.

Please add a 0.91 git tag for the revision from which the last PyPI sdist was produced would be appreciated

I'm creating a FreeBSD port, and will be using GitHub to fetch sources as the sdist is missing some desirable files (will create separate issues, PR's for these). When using GitHub for sources, its preferable to have exact git tags from which to fetch the tarballs, rather than using commit revision hashes

When env is specified for a jail in focker-compose.yml while exec.poststop is empty the resulting final exec.poststop is invalid, namely it contains the environment variables exports followed by an && operator while there is no command to follow.